Pouya LajevardiandClaude Opus 5
6bf1167624
The re-audit of the deploy-guard change surfaced defects well outside the diff, including one that would have broken production mail. docs/05-backend-spec.md had the two SES DKIM sets exactly inverted, labelling the three records that resolve as "orphans" and the three NXDOMAIN records as "Live. Never delete". Entry (j) corrected this in AGENTS.md §7 and the correction never reached docs/05. Since SES has no custom MAIL FROM, DKIM is the only thing satisfying DMARC, so acting on that table would have silently broken intake mail authentication. Also in this change: - .gitea/workflows/deploy.yml gains a guard as steps[0] that fails the run, naming the variable, if AWS_REGION, S3_BUCKET or CLOUDFRONT_DISTRIBUTION_ID is empty — how a Gitea too old for the vars context manifests. Verified fail-closed under bash -e, sh -e and bash -euo pipefail. - AGENTS.md Current Truth: SPF and DMARC recorded as present (Q20), the matching §10 High risk row retired, three duplicate Q rows removed. - docs/reference/AWS-Hosting-Guide.md tracked and given a do-not-execute banner; it was an executable procedure for the architecture D1/D3 replace. - Copy decks: "a working litigator" and "an active litigation practice" replaced with the register's own wording; LegalService JSON-LD replaced with ProfessionalService; tribunal-secretary offers removed per D14; nine stale question blockers swept. - astro.config.mjs: prefetchAll disabled — it injected JS into every page against the zero-JS convention with no decision recorded. - src/data/site.ts: unregistered response-time commitment nulled (Q27); OBA section names downgraded to [assumed] (Q28). - s3:AbortMultipartUpload reasoning corrected to measure ./dist, not the repo. Opens Q27, Q28, Q29. AGENTS.md entry (q) records the full resolution, including the findings declined and why. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012XquaEq4BgWMCwUqLEyNkF
1.9 KiB
description
| description |
|---|
| End-of-session ritual — update AGENTS.md under its constitution and hand back a clean state. |
Close out this session properly. The working file is the deliverable that outlives the session; a session that ends without updating it has lost its reasoning.
-
Re-read
AGENTS.md— the constitution at the top, then Current Truth. -
Update Current Truth in place wherever this session made a section stale: environment, decisions, the §4 register, open questions, risks. Re-stamp any fact you re-verified with today's date. A stale date means it needs re-checking, so do not leave a date you did not earn.
-
Append one Change Log entry, newest first, covering:
- what was discussed, decided, changed, or planned — decisions and plans count even if no code was written
- old → new for every change, and why
- findings you declined, with the reasoning
- anything deferred, and where it is now tracked
- questions closed and questions opened, by number
Never edit a past entry. If something earlier was wrong, correct it in today's entry and leave the original as written.
Any claim that a change was applied across files must cite the command and be written only after reading its output. Paste the
grep. Recall is not evidence — three entries on this project asserted a completed sweep and instances survived all three, one of them inside the definition of the agent whose job is to catch it. -
Check §12 Standing Reminders. Is anything now due? Should something new be added — a decision Pouya parked, or one you made on his behalf that he has not yet ratified?
-
Leave the tree clean.
git statusshould show only intended changes. No stray build output, no.env, no credentials, noaws-inventory.txt. -
Report: what changed in
AGENTS.md, what is open, and the single most useful next action.