chore(issue-templates): salvo-runbook AC should mandate compose.yml configs-wiring (no template enforcement today)

[bakeb7j0]

Summary

The salvo-runbook issue pattern in the sibling agent's project has 2 flights this campaign (#257, #258) that "forgot" the compose.yml configs-wiring step in their AC. The pattern is currently "established by example" — no template enforcement.

Scope question (worth resolving before expanding): is this a generic cc-workflow issue-template problem, or specific to the sibling project's salvo-runbook flavor? cc-workflow's /issue skill ships generic feature/bug/chore/docs/story templates — it doesn't have a "salvo-runbook" template. If the recommendation is to add one, the question is whether salvo-runbook is generic enough to live in cc-workflow or should stay in the project-specific skill set.

Severity: low — cosmetic AC enforcement; flights still ship.

Origin: Reported by sibling-campaign agent. @Scryer to expand and clarify the scope (cc-workflow generic template vs sibling-project-specific extension).

Implementation Steps

TBD — @Scryer to expand. Pick scope first, then write the template if it lives in cc-workflow.

Test Procedures

TBD.

Acceptance Criteria

• Scope decided: cc-workflow generic vs sibling-project-specific
• If cc-workflow: salvo-runbook template added to /issue skill with explicit compose.yml configs-wiring AC
• If sibling-project-specific: this issue is closed-as-misrouted with pointer to the right repo

Dependencies

• None

Metadata

Origin: sibling-campaign tracker. @Scryer owns expansion.