Add Background Bash Discipline to ensign shared-core (BashOutput polling)#122
Merged
Merged
Conversation
Document the BashOutput polling pattern for waiting on `Bash(run_in_background: true)` tasks, and the anti-pattern of a single blocking `sleep N && tail` sized to worst-case duration. Inserted between `## Rules` and `## Stage Report Protocol` in ensign-shared-core.md so both Claude and Codex ensigns pick it up. Refs: #183
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
…tatus: done) AC-1 re-verified, AC-2 dependency map written at implementation kickoff. AC-3 live diagnosis SKIPPED per dispatch step 3 (#183 is status: validation, PR #122 not yet merged — running AC-3 now would produce fo-logs whose timing is dominated by Category-B ensign blocking-sleep, defeating the symptom-(i)/(ii)/(iii)/(iv) distinction per the entity body's evidence- integrity rationale). Recorded AC-3 prep scaffolding (test invocation, artifact-capture snippet, per-event summary template, task_id emitter-attribution plan) so the next implementation pass can start AC-3 immediately after #183 merges. AC-4/AC-5/AC-6 SKIPPED as downstream of AC-3. AC-7 N/A in this blocked cycle (zero workflow diffs). No production-code edits.
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
…tatus: done) AC-1 re-verified, AC-2 dependency map written at implementation kickoff. AC-3 live diagnosis SKIPPED per dispatch step 3 (#183 is status: validation, PR #122 not yet merged — running AC-3 now would produce fo-logs whose timing is dominated by Category-B ensign blocking-sleep, defeating the symptom-(i)/(ii)/(iii)/(iv) distinction per the entity body's evidence- integrity rationale). Recorded AC-3 prep scaffolding (test invocation, artifact-capture snippet, per-event summary template, task_id emitter-attribution plan) so the next implementation pass can start AC-3 immediately after #183 merges. AC-4/AC-5/AC-6 SKIPPED as downstream of AC-3. AC-7 N/A in this blocked cycle (zero workflow diffs). No production-code edits.
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
1 participant
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.
Add a
## Background Bash Disciplinesubsection to the ensign shared-core so agents useBashOutputpolling on background commands instead of blockingsleep.What changed
## Background Bash Disciplinesubsection inskills/ensign/references/ensign-shared-core.md, between## Rulesand## Stage Report ProtocolBash(run_in_background) → BashOutput(bash_id) → status == "completed"polling loopsleep N && tailwastes wallclock and makes the agent uninterruptibleEvidence
(see #NNN), no temporal phrasing) inside the new subsectiontest_feedback_keepalive) does not exerciseBash(run_in_background=true), and the harness does not capture ensign-subprocess tool_use events; captain accepted SKIP#183