Validate DevIndex budget across three scheduled runs

Context

The implementation for #15745 is complete in #15747. The PR's current head ee315206603c9a808bcb2f6cf69fabcf4b46c25d is mergeable and all 16 reported checks pass, but its final acceptance criterion requires evidence from three scheduled Data Sync runs after the implementation reaches dev.

That evidence cannot exist while the implementation PR remains draft and unmerged. Neo also prevents reopening closed tickets through prevent-reopen.yml, so the post-merge witness needs a durable leaf of its own.

Problem

Keeping the three-run witness inside the implementation ticket creates a circular lifecycle gate:

1. #15747 cannot receive formal review while it remains draft.
2. The scheduled-run evidence cannot be collected before the PR is reviewed and merged.
3. Closing #15745 on merge and reopening it later would violate Neo's immutable issue-history contract.

Architectural Reality

• #15745 defines GraphQL cost as the DevIndex admission currency and reserves 100 points for the downstream label-index query.
• #15747 supplies the implementation and pre-merge test evidence.
• Scheduled Actions telemetry is the only evidence surface for the remaining operational witness.
• This ticket owns observation only; it must not become a second implementation lane.

Fix

After #15747 merges to dev, observe the next three scheduled Data Sync Pipeline runs that reach the DevIndex phase. For each run, record the run URL, tested head SHA, admitted-user count, observed GraphQL cost, remaining capacity, configured reserve, stop reason, and downstream label-index outcome.

Close this ticket once those three receipts demonstrate that DevIndex does not terminate on a GraphQL primary-quota or query-cost failure and that downstream work retains the declared 100-point reserve.

Contract Ledger

Decision Record Impact

none. This is a bounded operational-validation leaf for an existing implementation contract.

Acceptance Criteria

• #15747 is merged to dev.
• Three subsequent scheduled Data Sync Pipeline runs reach the DevIndex phase.
• Each receipt records the run URL, head SHA, admitted users, observed GraphQL cost, remaining capacity, configured reserve, and stop reason.
• None of the three runs terminates because of a GraphQL primary-quota or query-cost failure.
• The downstream label-index query completes without crossing the declared 100-point reserve in all three runs.
• A final evidence comment links all three receipts before this ticket is closed.

Out of Scope

• Further GraphQL-budget implementation changes unless the witness exposes a new defect
• GitHub App identity or repository/ruleset authorization
• Regeneration when dev advances during a run
• Raising the 200-user rollout ceiling
• Reopening or mutating #15745 after closure

Avoided Traps

• Blocking pre-merge review on evidence that only a merged workflow can produce
• Treating green CI as post-deployment evidence
• Closing this ticket after fewer than three qualifying runs
• Reopening the implementation ticket if a witness fails; a newly observed defect gets a new ticket

Related

• Implementation ticket: #15745
• Implementation PR: #15747
• Data Sync identity sibling: #15744
• Data Sync regeneration sibling: #15746

Live duplicate sweep: the latest 20 open issues by creation time, the latest 40 all-state A2A messages, repository labels, and ticket-memory results were checked immediately before creation on 2026-07-23 11:19 UTC; no equivalent open lane or active claim was found.

Origin Session ID: 72bb1088-8ed5-48b7-a835-c288cf30e814

Retrieval Hint: DevIndex GraphQL budget three scheduled runs post merge reserve validation