Automatically project advisory governance on product PR lifecycle

[shiny-code-bot]

Objective

Automatically project and refresh Launchplane's neutral governance checks from
trusted product pull-request lifecycle evidence instead of relying on a manual
operator projection call.

Finish Line

Every active product repository with advisory App coverage receives current
neutral Owner and engineering-review projections on the exact pull-request head
when relevant evidence changes. Product repositories submit only repository and
PR references through immutable trusted workflow identity; Launchplane derives
all head, tree, preview, policy, review, and Owner state server-side.

Current Status

State: Deferred post-endpoint automation work as of August 17, 2026.

The prior shadow canary dependency on #2159 and VeriReel PR #341 is retired. PR #341 merged without an Owner acceptance event, so it cannot provide the automatic-projection canary this issue originally expected. The current authoritative path is #2164, with draft VeriReel PR #343 as the truthful product candidate.

Automatic lifecycle projection is not required to reach the current endpoint. The manual authoritative Launchplane Owner path must first be merged, deployed, and prepared on the exact unchanged PR #343 head. This issue remains open for later server-owned or immutable reusable-workflow automation.

Next action after the current Owner endpoint: design one generic projection trigger, pin its trusted identity, and canary automatic exact-head projection without changing required checks, admission decisions, or notification policy.

Blocked by: no active dependency on #2159 or PR #341. Do not start this automation during the current no-contact endpoint.

Acceptance Criteria

• PR open, reopen, ready-for-review, and synchronize events trigger exact-current projection.
• Serving-preview or bound-evidence changes refresh the same exact-head check when the decision digest changes.
• Product callers submit only immutable repository identity and pull-request number references.
• Launchplane resolves head, tree, preview, affected products, policies, and human evidence server-side.
• Fork and untrusted workflow contexts cannot obtain projection authority.
• Workflow identity is pinned to an immutable Launchplane reusable-workflow revision or replaced by a server-owned event consumer.
• Projection failure remains advisory and cannot fail technical CI, merge admission, or the Owner event write.
• Changed heads receive distinct checks and cannot reuse prior Owner or engineering evidence.
• Existing projection names remain excluded from technical-check aggregation.
• Installation readiness from Manage advisory GitHub App coverage through product onboarding #2161 is checked before dispatch.
• Replay, drift, rate-limit, and provider-failure evidence is observable and retryable.

Relationships

• Superseded shadow-era canary: Make Owner acceptance discoverable and run the VeriReel canary #2159 and cbusillo/verireel#341.
• Current authoritative Owner cutover: Remove Owner acceptance shadow mode and make Launchplane authoritative #2164.
• Current truthful product candidate: cbusillo/verireel#343.
• App onboarding/readiness: Manage advisory GitHub App coverage through product onboarding #2161.
• Advisory projection foundation: Project advisory Launchplane governance checks through a GitHub App #2030.
• Engineering-review canary: Run truthful live engineering-review advisory check canary #2042.
• Ruleset/CODEOWNERS reconciliation: Reconcile GitHub rulesets and CODEOWNERS as projections #2031.
• Direct admission canary: Canary direct Owner-governed merge admission #2087.