[MODEL] Orchestrator's fixes left version/status wording on all 35 pages of a site until after the deadline, and its own brief added more

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude ignored my instructions or configuration

What You Asked Claude to Do

An orchestrator agent (Claude Code, Opus) was running worker agents on a small friends-guide website (35 pages, built from a repository and published to GitHub Pages). The user had a standing rule that version/status notes (revision numbers, 'being prepared', 'coming soon') appear only on one patch-notes page, and a launch deadline of 09:00.

What Claude Actually Did

• The user's written release definition of done had eight items (pages live, audio, trailer, message, etc.) and no wording check, so it passed 8/8 at 13:57 and again at 15:16 while every page still carried the wording.
• Measured from the repository's release commits: pages with the word 'revision' in visible text, excluding the patch-notes page: 34 pages with 101 mentions at the 09:00 deadline; 35 of 35 with 102 mentions at the 15:05 release; 90 at 15:36; 90 at 15:40; 80 at 15:41; 0 of 35 at 15:50. The header badge ('revision 7 is being prepared') had been on every page since 10-05 16:33.
• At 15:20 the orchestrator briefed a worker (brief delivered 15:23) to strip the 'being prepared' warnings and make the 'coming' wording present tense. The resulting commit (15:25) converted the header badge into 'revision 7 is live' on every page instead of removing it; it was published at 15:37.
• Two more fixes (15:39 and 15:41) each removed one specific line and left the rest.
• The wording was live until the Pages deployment finished at 15:51:20 to 15:51:25, about 6 h 51 min after the 09:00 deadline.
• The new check was added to the user's release gate at 15:52:08.
• Each fix was scoped to the phrases in its brief, not to 'every mention'.

Expected Behavior

When a user states a standing content rule more than once, the orchestrator turns it into a check over every page (not a list of phrases), runs it before reporting, and does not write a brief that adds the forbidden wording.

Files Affected

None. Agent messages and tool calls only.

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Sometimes (intermittent)

Steps to Reproduce

Not a deterministic repro. The sequence is in the record above; the underlying logs are on the reporter's machine and can be summarised on request.

Claude Model

Opus

Relevant Conversation

See "What Claude Actually Did". Quotes are limited to the agents' own tool results and messages.

Impact

Medium - Extra work to undo changes

Claude Code Version

2.1.289 (as recorded in the agent session logs; the claude on PATH reports 2.1.220)

Platform

Other

Additional Context

Related earlier reports from the same account: #99979, #100019. Timeline sources: the site repository's commit and Pages build times, and the gate's own result file.
Single-day record, 2026-10-06, all times US Eastern (Windows 11), a multi-agent session driven through a third-party agent harness; API platform is unverified. Reported as behaviour, not as a claim that Claude Code is defective.