Record the process.title and inherited-test-env findings as decisions - #1227
Merged
Conversation
Two findings from seq 1383 were only captured inside decision 192 and in task notes, where a future agent hitting the same walls would not look. 195 covers process naming for any spawn, not just terminal hosts: Bun accepts a process.title write on every platform and never throws, but it lands in the argv area on macOS (bounded by the original argv0, so it both silently no-ops on a short name and destroys a long one), in /proc/comm on Linux, and in the console title on Windows. argv0 is the carrier instead. 196 covers test isolation: suites started from an agent pane inherit that task's DEV3_TASK_* and, on the native backend, the host's DEV3_NATIVE_SESSION_*, which already broke a launcher assertion locally and only locally.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two findings from seq 1383 (PR #1221) were captured only inside decision 192 and
in task notes, where a future agent hitting the same wall would not look for
them. Both generalise well past native terminal hosts, so they get their own
records.
195 —
process.titleis not a process name under Bun. Applies to any spawnin the repo. Bun accepts the assignment on every platform and never throws, so a
smoke test that reads it back proves nothing. It lands in the argv area on macOS
(bounded by the original
argv0, so it silently no-ops on a short name anddestroys a long one), in
/proc/common Linux, and in the console title onWindows.
argv0is the carrier instead, and it does not disturb the child's ownprocess.argv. Also records which two viewer columns can never show anything butthe executable basename, and why per-task binary copies are not an option.
196 — Test isolation scrubs the agent's own task environment. Suites started
from a dev3 agent pane inherit that task's
DEV3_TASK_*and, on the nativebackend, the host's
DEV3_NATIVE_SESSION_*; CI inherits none of it. That alreadybroke
native-host-runtime.test.tslocally and only locally, on unmodified code.Documents the central scrub, and that a newly injected pane var must join
INHERITED_TASK_CONTEXT_ENVin the same change.Decision 192 now links to both. Documentation only — no code, no behaviour
change. No new changelog entry: this task's entry
(
feature-30-native-host-process-identity) already shipped with #1221, and thepolicy is one entry per worktree.