v1.23.1

frontend-production-engineer v1.23.1

A checkpoint release. No domain is added, and the router still carries
twenty-four. Twelve repairs, against ten items of the battery, in the operating
doctrine and in twenty of the twenty-four integrated domains.

Repaired

• 37 — fifty-one reference files, SKILL.md, README.md, AGENTS.md, and
  the Cursor rule: every one of them routed the reader to a repository that a
  public reader cannot install. The reader of this skill is never its author, so
  such a handoff names an owner nobody can reach, and the frontend rule then
  reads as incomplete. Three hundred references go, and every seam keeps its
  boundary: server-side work that the frontend must not perform now routes to
  the backend, which is an owner a public reader can act on.
• 38 — task-plan-and-scope-control: the table of the changes that stop a
  frontend task carried six such repositories in its owner column, and the
  checklist and the closing summary repeated two of them. The table keeps every
  row, because the classes of change are what a reader needs, and the column
  states the owner.
• 39 — twenty-four router clauses and thirty-one handoff lines: each one
  kept its subject and lost the name. Four clauses named two owners for one
  subject and now name one, because both resolved to the same place.
• 43 — README.md, AGENTS.md, and SKILL.md: three sentences addressed
  the owner of this repository rather than the person who installed it. The
  backend is out of scope, and the roster holds all twenty-four domains.
• 44 — SKILL.md, README.md, and the Cursor rule: five statements said
  that the router grows by one entry per release, that the invocation order
  applies as it grows, that six further domains follow the same pipeline, and
  that two folders arrive with a later domain. All twenty-four domains are
  integrated, so the four files state that.
• 44 — wcag-conformance-and-verification: one sentence said that the
  testing domain is not integrated yet. It landed four releases earlier, so the
  sentence sent the reader to nothing.
• 19 — wcag-conformance-and-verification and lint-format-and-scripts:
  both named the testing domain by number and slug with no loadable path. The
  runner, the fixtures, and the harness resolve to
  test-strategy-and-component-tests for the component lane and to
  end-to-end-journeys-and-flake-control for the browser lane, and the test
  layout to the first of those.
• 48 — README.md: the opening paragraph stated that the Django backend
  belongs to a set of skills that the reader has no way to install.
• 8 — instruction-files-and-skill-discovery carried no // Wrong: marker
  at all. It, task-plan-and-scope-control,
  version-proof-and-unconfirmed-code, and merge-gates-and-quality-signals
  opened a text fence with a bare
  Wrong:, Correct:, or Failure:. directory-and-module-boundaries already
  writes the comment form inside a text fence, and thirty-one marker lines
  take it.
• 30 — app-router-structure, bidirectional-layout-and-scripts,
  exposed-endpoints-and-destinations, keyboard-focus-and-live-regions,
  merge-gates-and-quality-signals, secret-boundary-and-supply-chain, and
  test-strategy-and-component-tests: seven descriptive sentences ran past
  twenty-five words. Each is two sentences now, and the break falls where a
  colon or a coordinator already split the thought.
• 30 — task-plan-and-scope-control,
  instruction-files-and-skill-discovery, security-headers-and-csp, and
  degradation-and-health-checks: six -ing forms stood as a noun or as a
  verb. The plan template read "each one naming the file it touches", and one
  file kept depth out of an instruction file "by moving" it.
• 31 — locale-formatting-and-calendars and SKILL.md wrote recognises
  against three uses of recognizes. performance-budgets-and-measurement
  introduced "the backend owner" where nine other uses say "the backend team".

Domains affected

• 01 nextjs-app-router-architecture — app-router-structure,
  caching-and-revalidation, and data-access-and-mutations.
• 02 typescript-type-system-discipline — boundary-validation-and-api-types.
• 04 project-structure-and-tooling — dependencies-and-git-workflow,
  directory-and-module-boundaries, and lint-format-and-scripts.
• 05 django-drf-api-contract — api-client-and-request-safety,
  cross-origin-and-bff-proxy, and openapi-schema-and-codegen.
• 06 data-fetching-and-state — server-state-and-query-cache.
• 07 authentication-and-authorization — route-protection-and-permissions and
  session-and-token-lifecycle.
• 08 realtime-and-streaming — live-events-and-cache-merge and
  push-transport-and-connection.
• 10 accessibility-wcag — keyboard-focus-and-live-regions and
  wcag-conformance-and-verification.
• 11 forms-and-validation — form-submission-and-server-errors.
• 12 data-tables-and-visualization — cell-formatting-and-export,
  charts-and-visual-encoding, and data-table-and-server-driven-state.
• 13 media-and-file-handling — file-upload-and-transport,
  image-and-video-delivery, and served-content-and-downloads.
• 15 ux-writing-and-content-design — error-and-empty-state-copy.
• 16 performance-and-web-vitals — paint-and-interaction-cost and
  performance-budgets-and-measurement.
• 17 frontend-security — exposed-endpoints-and-destinations,
  secret-boundary-and-supply-chain, security-headers-and-csp, and
  untrusted-markup-and-injection.
• 18 seo-and-metadata — crawl-and-index-control,
  route-metadata-and-social-cards, and structured-data-and-rich-results.
• 19 internationalization-and-rtl — bidirectional-layout-and-scripts,
  locale-formatting-and-calendars, and locale-routing-and-catalogs.
• 20 testing-and-quality — end-to-end-journeys-and-flake-control,
  merge-gates-and-quality-signals, network-mocks-and-contract-tests, and
  test-strategy-and-component-tests.
• 21 observability-and-resilience — correlation-and-telemetry,
  degradation-and-health-checks, and error-capture-and-reporting.
• 22 build-deploy-and-runtime-ops — build-output-and-container-image,
  release-pipeline-and-rollback, and runtime-process-and-reverse-proxy.
• 23 analytics-privacy-and-consent — consent-gate-and-cookie-inventory,
  data-rights-and-privacy-surfaces, and event-taxonomy-and-tracking-plan.
• 24 agent-operating-doctrine — instruction-files-and-skill-discovery,
  task-plan-and-scope-control, and version-proof-and-unconfirmed-code.

The version moves from 1.23.0 to 1.23.1. This run adds no domain, so the router
still carries twenty-four and the minor number stays at 23. This run changed
fifty-three reference files and five files outside references/, so the patch
number moves by one. The frontmatter description is unchanged at 1013
characters.

Limits

• The router rows, the trigger groups of the Cursor rule, and the frontmatter
  description are enumerations of Technical Names. The sentence-length rule
  does not shape them, and this run applied it to none of them.
• The standard holds an instruction to twenty words and a descriptive sentence
  to twenty-five. These files are descriptive rules rather than a procedure, and
  four earlier checkpoints read them that way, so this run enforced the
  twenty-five. Forty-five rule statements run from twenty-one to twenty-five
  words on that reading, and none moved.
• Nine reference files had never met this battery, because domains 22, 23, and
  24 landed after the 1.20.1 checkpoint. Each was read in full. Six of the
  twelve repairs reach into them, and three sit there alone.
• Sixty-four reference files met the battery at an earlier checkpoint. This run
  tested them with the mechanical sweep: the router resolution, the orphan
  search, the hyperlink and marker searches, the Next 15 idioms, the pair and
  checklist polarity, the rg --files-without-match convention, the seam
  resolution, the invisible-character scan, the dialect count, the noun-cluster
  scan, the warning placement, and the sentence-length rule. Six of them carried
  a repair.
• No TypeScript compiler and no Node runtime for this stack are installed on the
  machine that ran this checkpoint. Every code sample was read against the
  pinned versions, and none was compiled.
• This run added no material, so it opened no forward seam. Every seam that it
  changed points at a file that exists today, or at an owner outside this
  repository that the text names in its own right.
• One // TODO: remains, inside a Correct sample that teaches how to record a
  schema gap against a ticket. It is the rule that the sample states, and not an
  unfinished note.
• Two http:// tokens remain, in an Nginx proxy_pass line. Nginx requires the
  scheme, and the value names an upstream block rather than a host.