v1.23.4

frontend-production-engineer v1.23.4

A reconcile release. The build is complete: all twenty-four domains are
integrated, and the router carries every one of them. No domain is added. Five
repairs, against five items of the battery, in README.md and in the three
files that carry the same content to the other agents.

Repaired

• 2 — README.md: the roster marked every domain as integrated and named
  no file that carries it. A reader who wanted the depth behind a domain had
  the router table as the only route to it, and the router is keyed by concern
  rather than by domain. Each of the twenty-four rows now names its files.
  The seventy-three files partition across the roster, each one under exactly
  one domain.
• 4 — README.md: the layout tree listed every other top-level entry,
  including the dot-directories and .gitignore, and omitted the two
  workflow files. The sentence under the tree states what the repository does
  not hold, so the tree reads as complete. The two files are in it now, with
  what each one gates.
• 8 — AGENTS.md, GEMINI.md, and the Cursor rule: none of the three
  stated the order in which a feature task resolves the domains. Two of them
  named the tiers, which is a taxonomy and not an order, and the third named
  nothing. An agent that reads one of these files alone had no rule that puts
  the backend contract before the code that calls it. All three now state the
  order.
• 10 — AGENTS.md, GEMINI.md, and the Cursor rule: none of the three
  named the seven domains that hold a veto over completion. A reader of one of
  these files could run the four commands, pass all four, and never learn that
  a keyboard trap or an injection sink is a failed task. All three now name
  the seven, with the first failure condition of each, and each one points at
  the full list.
• 11 — GEMINI.md: it stated the standing rules and the conflict rule, and
  it stated no check at all. It deferred the definition of done to the
  canonical file, so the one agent that reads only a context file had nothing
  to run before it reported the work complete. It states the six conditions
  now.

Domains affected

• None. This run changed no reference file, so no domain moved. The four
  cascade files changed, and SKILL.md changed for the version string alone.
• The three cascade files now name the seven blocking domains:
  01 nextjs-app-router-architecture, 02 typescript-type-system-discipline,
  05 django-drf-api-contract, 07 authentication-and-authorization,
  10 accessibility-wcag, 17 frontend-security, and
  20 testing-and-quality.
• README.md now maps all twenty-four domains onto the seventy-three files
  that carry them.

The version moves from 1.23.3 to 1.23.4. This run adds no domain, so the router
still carries twenty-four and the minor number stays at 23. This run changed
five files, none of them under references/, so the patch number moves by one.
The frontmatter description is unchanged at 1013 characters.

Limits

• Thirty-six items ran. Thirty-one passed on the first read, five failed, and
  each of the five was re-tested after its repair. The re-test is the same
  command that found the failure.
• The blocking lines in the three cascade files carry the first failure
  condition of each gate, and not the whole gate block. Reproducing seven gate
  blocks would make these files copies rather than pointers, which is what the
  head of AGENTS.md states they are not. Each file names the canonical file
  as the holder of the full list.
• The denylist search returns zero hits across the full tree, and it returned
  zero before this run as well. No seam lost a name in this pass, so no seam
  needed its boundary restated.
• One term for one thing holds across the tree. Two deviations sit inside code
  and stay: a British spelling in one thrown error string, and an American
  spelling in one code comment. Both are exempt under the language standard.
• The six https:// tokens in README.md are the clone address of this
  repository, which every install instruction needs. Two http:// tokens
  remain in an Nginx proxy_pass line, where the scheme is required and the
  value names an upstream block rather than a host.
• Thirty-four tags and thirty-four published releases match one for one. None
  is a draft and none is a prerelease.