Delete or collapse obsolete shared prompt fragments

[jrpbuilds]

Parent

Part of #46.

Relationships

Depends on #57, #58, #59 and #60.

Goal

Remove shared prompt fragments that only exist to teach workflow mechanics now owned by runtime/tooling, and collapse surviving shared guidance to the smallest genuine semantic contracts.

Scope

Audit every file under prompts/shared/ after the role rewrites land.

Strong candidates for deletion or major collapse include fragments around:

• parallel progress reporting;
• background dispatch bookkeeping;
• planning batches/scheduler behaviour;
• handoff gating that is now machine-validated;
• repeated remediation/re-review mechanics;
• repeated worktree/concurrency rules;
• duplicate lifecycle/archive safety prose only where the final Consolidate workflow legality behind one canonical derivation #50/Rewrite Coordinator prompt as a minimal orchestration contract #57 runtime boundary genuinely enforces the same invariant.

Specific current candidates include parallel-progress.md, background-dispatch.md, planning-batches.md and handoff-gate.md, but the implementation should decide based on the final v1.7 runtime contract rather than preserve files for compatibility with old prompts.

Retention rule

A shared fragment should survive only when:

1. multiple agents genuinely need the same semantic guidance; and
2. that guidance cannot be more reliably expressed through permissions, validation, tool schemas or dynamic dispatch context.

Conversely, do not delete a semantic guardrail merely because an adjacent lifecycle mechanic moved into TypeScript. If #50 determines that an invariant such as archive-after-successful-review is not yet canonically enforceable, preserve the smallest prompt guidance that still protects it, following #57.

Shared files should not become a hiding place for the old Coordinator manual.

Include hygiene

• Remove includes that become empty/redundant.
• Keep include resolution simple; do not introduce a prompt inheritance DSL.
• Ensure no role prompt receives a fragment purely because another role used to need it.
• Prefer a few concise shared contracts over many tiny cross-referenced procedural fragments.

Acceptance criteria

• Every surviving prompts/shared/* file has a clear semantic reason to exist.
• Obsolete Todo/progress/runtime bookkeeping prose is deleted.
• Lifecycle/archive prose is removed only where tooling fully replaces the protected invariant.
• Any still-model-owned lifecycle invariant is retained only in its smallest necessary form.
• Includes remain acyclic and package/runtime loading continues to work.
• No deleted fragment's behaviour is lost unless it has moved to runtime/tooling or was demonstrated unnecessary.
• Prompt tests are updated away from requiring obsolete fragment names/phrases.
• Packed npm smoke tests confirm required prompt assets still ship.
• Total expanded prompt sizes are materially lower after shared-fragment cleanup.

Out of scope

• Adding a complex user-override/inheritance system.
• Reintroducing workflow mechanics into different shared files.
• Inventing deterministic archive/review state to justify deleting prompt guidance.
• Final regression budget values; tracked separately.