[ANT1OFF]

Stacked on #89, the prompt size budget; these additions stay within it. Merge after #89.

What changes

Small changes to role text that every orchestrator and worker reads. Each one is quoted below exactly as it now reads. Nothing else changes.

(a) A worker's report says what it ruled out (prompt.ts, worker role)

In the report line, "Keep the summary short and factual." now reads:

Keep the summary short and factual, and say what you tried and ruled out, not only what worked.

(b) Check before repeating an outside action after a restart or cut-off

New line in the worker role (prompt.ts), after "Report, then end your turn…":

• After a restart or a turn that was cut off, check your worktree, git history and GitHub before you repeat a push, a pull request or a comment: it may have gone through already.

The cut-off notice a worker is sent when a restart continues it is restartContinuation in rules.ts, sent by the boot path (service/boot.ts → noteRestart). Its old phrase "Continue where you left off, after checking what state your work was left in." now reads:

Continue where you left off, after checking your worktree, git history and GitHub: don't repeat a push, a pull request or a comment that already went through.

The orchestrator's away-digest note on cut-off workers (restartNote in rules.ts) gains one sentence after the list of workers. Whether to set a worker going again stays the orchestrator's decision:

Before you set one going again, have it check its worktree, git history and GitHub so no push, pull request or comment goes out twice.

(c) Briefs attach the user's words and invent nothing (prompt.ts, orchestrator role)

The userMessages line used to read: "When the user pasted something the worker needs as it is (a log, a spec, an error, a long list), don't retype it into the brief: pass userMessages … The brief still says what to do with them." It now reads:

• When a brief comes from what the user asked, attach their words rather than retyping them, above all a paste the worker needs as it is (a log, a spec, an error, a long list): pass userMessages with how many of the user's latest messages in this conversation to attach, and Gram copies them word for word after the brief. Do the same on send_message to a worker. The brief still says what to do with them, and adds no requirements, acceptance criteria or checklists the user didn't ask for.

The brief-writing guidance before it ("A worker sees only its brief… Write the brief so it stands alone: …") is unchanged. The orchestrator still writes briefs, and a test now asserts that line remains.

Size (characters, measured with the budget test's inputs)

Role	System prompt before	after	Total after (prompt + tools)	Limit from #89
orchestrator	20,112	20,243 (+131)	59,504	62,400
worker	5,998	6,237 (+239)	33,261	34,700
plain	302	302	22,669	23,900

Everything stays within budget, so nothing was trimmed. Tool definitions are unchanged.

Tests

• rules.test.ts:
  • the worker prompt carries (a) and (b);
  • the orchestrator prompt carries (c) and still says "Write the brief so it stands alone";
  • restartContinuation carries the check;
  • restartNote's exact string is updated.
• bun run test packages/server/src/orchestration/rules.test.ts packages/server/src/orchestration/service-restarts.test.ts packages/server/src/orchestration/prompt-budget.test.ts packages/server/src/orchestration/workspace-pause.test.ts: all passed (437 before the last wording change to restartNote; 431 on the final run, which left out the budget and pause files).
• GOMEMLIMIT=2GiB bun run typecheck --singleThreaded, bun run lint, bun run fmt:check, bun run check:scaffold: pass

Known limits

• Synthetic only: the text is asserted, not how live agents behave with it.
• This is general harness behaviour, not Gram's own repo process: nothing here names a Gram-specific workflow.