docs(ignition): acceleration ruling — front-load count, parallel Phase IV, flip pre-build

[kyle-sexton]

Dated Phase-4 note: operator ruling (2026-07-22) to move at maximum speed within the predicate's intent. Calendar gates stay binding; sanctioned levers are front-loaded seeding (genuine items only), parallel Phase IV ignition (gate already met), and pre-built Phase III flip machinery. Records same-day watch activity: drain PRs #23/#24/#26 + Dependabot #25 merged, queue reseeded (scratch#27–#31), predicate completions=6.

Related

• Pin gate runner image to ubuntu-24.04 kyle-sexton/autonomy-demo-scratch#27–chore: sync standards configs #31. No linked issue — status-note documentation; nothing in this repo closes.

🤖 Generated with Claude Code

[claude]

Claude finished @kyle-sexton's task in 55s —— View job

---

PR Review

• Read PR diff and changed files
• Review against CLAUDE.md and project guidelines
• Assess correctness, security, and alignment
• Post findings

---

Summary: This PR adds two cross-references to melodic-software/standards conventions/engineering/shareable-artifact-design.md in docs/PLUGIN-PHILOSOPHY.md — one inline citation in the "Design boundary" section and one entry in "Authoritative references". The intent is to clarify that the plugin design rules here specialize an upstream, artifact-agnostic doctrine rather than originate independently.

---

Findings

Minor prose defect — missing "that" in the references entry

docs/PLUGIN-PHILOSOPHY.md line 391–393:

- `melodic-software/standards` `conventions/engineering/shareable-artifact-design.md` — the
  artifact-agnostic consumer-facing design doctrine the design boundary, configuration ownership,
  and setup contract above specialize for plugins.

Reads as a noun pile: "doctrine the design boundary … specialize" is grammatically ambiguous without "that". The design-boundary inline text (line 14–17) gets this right ("this document specializes it…"), but the reference bullet drops the relative pronoun. Should read:

…the artifact-agnostic consumer-facing design doctrine that the design boundary, configuration ownership, and setup contract above specialize for plugins.

Fix this →

---

No concerns on:

• Security — pure documentation, no code execution surface.
• Architecture — correctly identifies the upstream owner and limits the specialization claim to plugin-specific additions only.
• CLAUDE.md guidelines — doc-only, no manifest schema changes; no fresh-docs fetch required for internal philosophy docs.
• Style consistency — reference formatting matches the existing melodic-software/standards bullet below it.

One typo-level prose fix needed; otherwise the changes are clear and accurate.

[kyle-sexton]

Mis-created: a parallel-session commit landed on this branch via a shared-checkout race; the intended change ships separately. The stray commit (4f48d5a, PLUGIN-PHILOSOPHY.md) is preserved on its own lane's branch.