C-416: GI and cycle projection reconciliation — carried-forward GI made visible in cycle.json

epicon_id: EPICON_C-416_GOV_gi-cycle-projection-reconciliation_v1
ledger_id: cursor-aurea-c416-gi-reconciliation
scope: docs, ci, specs
mode: normal
issued_at: 2026-08-27T00:00:00Z
expires_at: 2026-11-20T00:00:00Z
justification: |
  VALUES INVOKED: integrity, transparency, operator truth
  REASONING: cycle.json's own gi field has been carried forward unattested since C-410 (Civic-Protocol-Core's ledger pulse has returned gi=null every day in that span; load_gi_state() has no wired writer for GI_STATE_JSON/GI_STATE_PATH). scripts/run_state_sync.py already detected this every run — a CI ::warning:: and a journals/cycles/<cycle>.json field — but neither cycle.json nor STATE/writer-health.json ever surfaced it, so a reader of the "authoritative" cycle pointer alone had no signal the value was stale. Separately, the C-415→C-416 propagation gap reported this morning across Terminal/cycle.json/HIVE traces to mobius-bot-state-sync.yml firing ~11h late (15:09 UTC vs its 04:10 UTC schedule) — ordinary GitHub Actions cron slippage, not a defect, and needs no code fix. This EPICON reconciles both by provenance rather than averaging or copying one surface's number over another's.
  ANCHORS:
    - scripts/state_sync_cycle.py apply_cycle_writer_hygiene() / gi_attestation_status()
    - schemas/cycle_state.schema.json (gi_attested_this_cycle, gi_withheld_reason)
    - docs/protocols/agent-reporting-protocol.md §1a (three distinct GI surfaces)
    - civic-protocol-core-ledger /pulse/state (gi: null, C-410 through C-416 observed)
    - mobius-bot-state-sync.yml run history (GH Actions, 30-day window; C-416 run at 2026-08-27T15:09:05Z vs 04:10 UTC schedule)
    - C-410 precedent: commits 92b8839 / 55e3b43 / 4c98f99 (operational_pulse / competing_projections fields, scrubbed on rollover by design)
  BOUNDARIES: Does not modify GI calculation, average measurements, mutate KV, advance cycle.json's current_cycle/date/gi manually, lift gates, unlock Fountain, seal C-416, or deploy. Civic-Protocol-Core's load_gi_state() wiring gap is documented as a finding, not fixed here — that repair is a GI-calculation change outside evidence-and-schema-proposal authority.
  COUNTERFACTUAL: If ZEUS or a later cycle finds gi_attested_this_cycle/gi_withheld_reason conflict with a downstream consumer's schema assumptions, narrow the fields further or revert — additive-only change, trivially revertable.
counterfactuals:
  - If tests fail, do not merge
  - If cycle.json's current_cycle, date, or gi value is found mutated by this change, revert immediately
  - If MII drops below 0.95, revert immediately