docs(agents): the Playwright specs have been in CI since 2026-08-08

[mforce]

Closes #767

AGENTS.md's #394 rule and its decision record both state that tools/simulation/k6/ and the
Playwright specs in tools/simulation/ui/ are uncovered by CI. Half of that stopped being true on
2026-08-08, and it is the half a reader is most likely to act on.

The evidence

.github/workflows/e2e-smoke.yml runs on: pull_request, path-filtered to src/**, web/**,
tools/simulation/**, deploy/**, the three root image-build inputs and the workflow itself. Its own
header dates the change:

The quick suite runs ON PULL REQUESTS (owner call, 2026-08-08, revising the …)

A write-contract change lives in src/ by definition, so the Playwright specs run for exactly the
class of change this rule governs. Roughly 28 specs across 14 files, about three minutes. Only slow
(the real 15-minute token-expiry spec) and canary stay dispatch-only, and a docs-only PR skips the job.

.github/workflows/k6-baseline.yml is still workflow_dispatch: only, so k6 is genuinely
uncovered, exactly as the rule says. Everything about its tolerated-status list letting a broken
write pass against a 100% green baseline is unchanged, and it is the sharper trap of the two.

Observed rather than inferred: on #766 the check "Playwright smoke over the simulation fixture" ran
and passed, and that run included worker-sale-allocation.spec.ts, which carries no slow or canary
tag. The decision record was the more specific and more wrong of the two — it said the specs were
"workflow_dispatch only, #385".

Why it is worth correcting

The error points the safe way: it makes you verify by hand something CI already covers, so nothing
has shipped broken because of it. The cost is misdirected effort. On #727 the Playwright half of the
#394 caller read was done by hand under the belief that a green baseline would hide a break, when CI
would have caught it. It also flattens the one caller that genuinely still needs reading into a list of
two, which makes it easier to skip.

It is a trap in the other direction too. Anyone who checks the workflow, sees Playwright is covered and
concludes the whole bullet is stale will stop reading the k6 callers as well.

What changed

AGENTS.md — the bullet now separates the two, names the mechanism rather than the state (since the
state has moved once already), and keeps the rule's durable half: verify by reading, because CI can
tell you a spec broke but not that a caller's intent changed.

docs/decisions/394-write-contract-callers.md — a dated amendment rather than a rewrite. What the
record said was true when it was written, and a decision record that quietly reflects later facts stops
being a record. The original paragraph keeps its one factual correction (k6-baseline.yml named
explicitly, the false Playwright clause removed) and the amendment explains what moved and when.

Not in scope

Whether the path filter should also cover a docs-only PR that changes a spec's expectations. It should
not, but that is a separate argument from this correction.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 392ad4d3-46db-48aa-be88-14deee68ba0d

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}