Repository navigation
SMOKE TEST: cross-repo dispatch from openchamber — safe to close #1569
Description
This is a standing smoke test of the pm-dispatch grants mesh, filed from developing-today/openchamber via the pm-dispatch-queue reusable action (developing-today/code#2672). It proves that one fleet repo can queue a task and file a tracking issue in another fleet repo (here: developing-today/opencode). No action is needed; this issue and its queue task are cleaned up after each run.
Acceptance criteria
- The cross-repo dispatch smoke test completes its proof: this issue and its queue task were created in developing-today/opencode by an openchamber-origin dispatch (code feat: Configure project for Vercel deployment anomalyco/opencode#2672 grants mesh).
- Cleanup after the run closes this issue; no fleet work is expected or performed on it.
Activity
developing-today commentedon Nov 3, 2026
Filed by pm-dispatch (GitHub Actions OIDC (repo developing-today/openchamber, actor dezren39, workflow developing-today/openchamber/.github/workflows/pm-dispatch-smoke.yml@refs/heads/main)).
dezren39 commentedon Nov 4, 2026
Intake review
Fleet monitor intake pass (protocol §5), 2026-11-04.
Notes: standing pm-dispatch smoke test — 'safe to close' per its own body; not fleet work and not a defect. This intake pass only normalizes it (priority/effort/kind + meta/enriched) so it stops surfacing as an unenriched candidate; its queue task and cleanup belong to the dispatch smoke cycle. Risks: none. Suggested approach: none — leave to the smoke cycle's cleanup.