fix: sweep D3 amendment through the specs; correct inverted DKIM table

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

docs/03-content-spec.md

@@ -29,7 +29,8 @@ detect padding instantly and discount everything after it.
 - Concrete nouns. *Lien claim. Change order. System Impact Assessment. Model
   card. Minutes of settlement.* Specificity is the credential.
 - Name the limits. "Sole-arbitrator appointments follow the Q.Arb designation;
-  co-arbitration and tribunal-secretary work is available now." Precision about
+  co-arbitration work is available now." (**No tribunal-secretary work** — D14
+  removed the rate and bars offering it; see `docs/07-fees.md`.) Precision about
   what you cannot yet do makes the rest believable.
 - Plain words over Latin. "Without prejudice" survives because it is a term of
   art; *inter alia* does not.
@@ -49,8 +50,9 @@ detect padding instantly and discount everything after it.
 
   This framing is **interim** — see `AGENTS.md` §12 R1. Raise it with Pouya
   rather than letting it settle in by default.
-- Superlatives. No "leading", "premier", "top-rated", "best". LSO marketing rules,
-  and they read as insecure.
+- Superlatives. No "leading", "premier", "top-rated", "best". They are
+  unverifiable, they read as insecure, and marketing rules for regulated
+  professions treat them as suspect.
 - Outcome language that could be read as a guarantee.
 - "Passionate", "dedicated", "committed", "proven track record", "results-driven",
   "leverage", "synergy", "solutions".
@@ -68,7 +70,7 @@ detect padding instantly and discount everything after it.
 Reused, adapted, across the hero, the About page, and the PDF bio:
 
 > The dispute resolution practice of Pouya Lajevardi — a credentialed neutral
-> who is also a working litigator and a practising machine-learning and
+> who is also close to live litigation and a practising machine-learning and
 > infrastructure engineer. Built for commercial, construction, energy,
 > technology, and cross-cultural disputes that turn on facts most neutrals take
 > on faith: the contract, the code, the engineering documents, and the
@@ -115,7 +117,7 @@ redrawing the loop into a line.* First person: "my mark", not "our mark".
 
 ### About
 400–600 words of narrative, then structured credentials. Tell the three tracks
-as one arc, not three lists: a JD and an active litigation practice; a parallel
+as one arc, not three lists: a JD and active litigation exposure; a parallel
 career in machine learning and infrastructure engineering; a company run
 alongside both. The arc is the point — the credentialing pathway from Q.Med
 through Q.Arb to C.Med-Arb is stated openly as in progress. The brief treats
@@ -150,7 +152,8 @@ Five steps with real timing. Say what happens if the matter does not settle —
 counsel want to know the downside shape before they commit a client's day.
 
 ### Fees
-**Blocked on Q4.** Real numbers or `TODO(pouya)`. Plain table, no "starting from"
+**Unblocked — Q4/Q14 answered, D14.** Build from the confirmed card in
+`docs/07-fees.md`. Plain table, no "starting from"
 evasions, no "contact for pricing" after promising a rate card.
 
 ### For parties