[REPPL]

Holds the prompt hook's output under the host's 10,000-character cap, and sends the shell rules only where they can change what an agent does.

Above that cap the host saves the hook's output to a file and shows the agent a short preview, so most of what abcd sends on a busy prompt never reaches the agent. Measured live on the released binary: 38,582 bytes written, 1,543 shown. On this branch the same kind of prompt wrote 8,761 bytes, and all of them were kept.

What changes

• The prompt hook has one budget. The status and away blocks are read first. The rules and memory notes share what is left, and the notes keep a floor. Note room that goes unused returns to the rules.
• A domain that does not fit shrinks instead of being cut. It goes as its first rule and the command for the rest, or the command alone. With no room for that, it waits a turn.
• The shell rules split by what the guard does. Ahead of time, the agent gets a line about the guard and the rules that only warn. What the guard refuses, including a delete it cannot prove safe, reaches the agent at the refusal. abcd rules SHELL lists every rule. A repository's own rewording of a delete rule stays in the rules it sends ahead.
• With the guard off, the hook says so. It sends one line saying nothing refuses or warns, the command for the list, and no hazard text.
• SessionStart, which already kept under the cap, now reads the same constant as the prompt hook.
• The old whole-output injector and renderer, which no production code calls any more, move into the rules package's test helpers.

What to know before relying on this

• No reservation was taken: a build pushes one, and this work was to push nothing until it was finished.
• The intent audit found 3 criteria met, 5 met with concerns and none unmet. It read the branch at d287ede. The listing heading it flagged was fixed afterwards in 12994e1, and that fix was reviewed but not audited again.
• Criterion ac-5 was reworded after the first audit, under the person's delegation, with no separate sign-off.
• Of the intent's conditions, one is untested, one survived and one was narrowed.
• CONCURRENCY (11,406 bytes), and with a long note ATTRIBUTION and LOAD, go short on a turn until the rule-by-rule review trims them. Their first rule and the command still reach the agent.
• The whole-output test does not exercise the status block.
• The docs fidelity receipt is for an earlier tree. A cut on the default branch needs its own review anyway.

iss-2611070830056851 is filed here and stays open: with the person away, the stop check names one session's work to every session on the account.

Resolves: iss-2611041419354106
Delivers: itd-2611041636196213
Refs: iss-2611070830056851
Assisted-by: Claude:claude-opus-5-5