fix(intake): fire welcome + case brief on the label race (closes the #44 dead-end)

[michaeloboyle]

Problem

Real submissions dead-end at status:pending-review. #44 (Brad Ross / bar181, "AI Symbolic Protocol", opened 2026-08-10) is the live proof: 11 days, no committee case brief, no notification, no score. Zero real upstream submissions have ever moved past pending-review.

Root cause (verified from the Actions history): on 2026-08-10T16:26 when #44 opened, both On Submission and Governance Agent ran and → skipped. Both are gated on issues: types: [opened] + contains(labels, 'status:pending-review'). The project-submission template applies that label at creation, but it is not reliably present in the opened event payload (a well-known GitHub race), so the guard is false and the workflow skips, then never re-fires. pages.yml survived only because it also listens to the labeled event.

Fix

Add labeled to the issues trigger on both workflows and guard on:

(action == 'labeled' && label.name == 'status:pending-review')
|| (action == 'opened' && contains(labels, 'status:pending-review'))

Plus an idempotency check in each script (skip if the welcome / case brief is already posted) so opened and labeled cannot double-post.

Verification done

• YAML parses (both files).
• Trigger logic fires exactly once in both the race path (opened skips, labeled runs) and the non-race path (opened runs, labeled short-circuits on the idempotency guard).

Not covered here (follow-ups filed)

• fix(accuracy): OIA auto-classifier produces near-universal false positives from .github boilerplate #48 classifier false positives, test: OIA classifier + pending/promote pipeline has zero test coverage #49 OIA test coverage, chore: enforce OIA server/client classifier twin-sync in CI #50 twin-sync.
• The committee still has to actually score [Project Submission] AI Symbolic Protocol #44 once notified. This PR restores the notification; it does not substitute for the human scoring step.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes a GitHub Issues label race that caused real project submissions to stall at status:pending-review by ensuring the intake workflows run when the status:pending-review label is applied (via labeled), while adding script-level idempotency guards to avoid double-posting.

Changes:

• Update On Submission workflow to trigger on issues.labeled as well as issues.opened, with an action-aware guard for status:pending-review.
• Update Governance Agent workflow similarly, adding an idempotency check before generating/posting the case brief.
• Append a new RVF attestation transition entry and normalize the existing JSONL line formatting.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
data/rvf/attestation.jsonl	Adds/normalizes case-brief-generated transition entries for the RVF audit trail.
.github/workflows/on-submission.yml	Adds labeled trigger + guarded condition and a welcome-post idempotency check for intake.
.github/workflows/governance-agent.yml	Adds labeled trigger + guarded condition and a case-brief idempotency check to prevent duplicates.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.