meta: cross-repo pipeline communication protocol — radcap owns coordination

[sfegette]

Context

radcap serves as the canonical owner of the shared Apple CI/release pipeline across all of Scott Fegette's Apple platform repos: radcap, grapfel, and chordale (and any future additions). This issue documents the reciprocal obligations that come with that ownership — both what radcap owns and what it must do when things change.

---

What radcap owns

• The canonical `release.sh` + `release.yml` + self-hosted runner pattern
• Self-hosted runner registration and service management on the dev machine
• The keychain unlock pattern for CI codesigning
• Cross-repo decisions about pipeline architecture, secrets management, and distribution strategy
• Scaling the pattern to new Apple platforms as they're added

---

Radcap's obligations to downstream repos (grapfel, chordale)

When radcap changes the canonical pipeline pattern:

1. Open an issue (or PR) in each affected downstream repo describing what changed and what needs to migrate
2. Don't consider the change "done" until downstream repos are notified — drift is how grapfel#52 happened
3. Label pipeline-related issues with a consistent prefix (ci: or a pipeline label) so they're easy to triage

When a pipeline bug or improvement is discovered in any repo:

• If it's a live risk (could break CI now): the discovering agent files at sfegette/radcap immediately, no user gate
• If it's an improvement/nice-to-have: flag to user first; user decides whether to escalate here

---

Downstream repo protocol (for reference)

grapfel and chordale agents are expected to:

• Check radcap for the current canonical pattern before proposing any change to .github/workflows/ or scripts/release.sh
• Mirror radcap's solution exactly rather than inventing a new one
• File live pipeline risks at sfegette/radcap (not just in their own repo)

---

Current pipeline state (2026-06-09)

Repo	Runner	release.sh	Status
radcap	✅ online	✅ canonical	good
grapfel	✅ online	✅ fixed (grapfel#52 → 6fd9299)	good
chordale	⏳ pending chordale#49	⏳ not yet	blocked on runner

---

Boss

Scott is the boss. Just wanted to be clear about that.

/cc @sfegette

[sfegette]

Standing rule from Scott (2026-06-09): Always err on the side of over-communication between agents and repos. When in doubt about whether something is worth flagging — it is. Don't wait for confirmation. Don't batch signals. File early, file often.

Radcap's agent should apply this norm actively: if you notice anything that might affect grapfel or chordale's pipeline — a change, a risk, an ambiguity — open an issue in the affected repo immediately. Urge grapfel's and chordale's agents to do the same in return.

The cost of a noisy issue is low. The cost of a missed signal across three repos is not.

[sfegette]

🤖 radcap agent — 2026-06-11 — chordale#49 spec written; runner pending

Chordale#49 has a complete spec: release.sh + release.yml + export plists + App Store Connect upload pattern, all written up.

radcap's obligation per this issue: Register ~/actions-runner-chordale on the dev machine once chordale's scripts are implemented and merged. Watching chordale#49 for the "implementation complete" signal. Will handle runner hookup at that point — no user action needed until the scripts land.

Current pipeline state:

Repo	Runner	release.sh	Status
radcap	✅ online	✅ canonical	good
grapfel	✅ online	✅ (grapfel#52 fix)	good
chordale	⏳ pending chordale#49	⏳ not yet	blocked on implementation

[sfegette]

🤖 Claude Code [bmw-dev-stack] — 2026-06-13 — Branch purge + sentinel-sec wired

Cross-repo actions taken on sfegette/radcap this session (from bmw-dev-stack meta-agent, on Scott's instruction):

Branch purge: All 7 non-main branches deleted — radcap is now main-only.
Deleted: codex/fix-18-20-countdown-writer-errors, codex/fix-19-capture-hot-paths, codex/fix-21-teleprompter-privacy, codex/fix-22-recording-accessibility, codex/fix-23-social-video-presets, feat/agent-role, fix/29-camera-warmup. PR#28 (social video presets, stacked on closed PR#25) was also closed as orphaned — issue #23 remains open for a fresh PR.

Sentinel-sec wired: radcap now has the sentinel-sec webhook (https://n8n.scottfegette.com/webhook/sentinel-sec, issues events) and the sentinel-sec label. Applying that label to any issue triggers an automated n8n security review.