A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I1403

Backfill the projection once, deliberately, and record what it created

Where it stands

devtask.issue

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: work-graph-github
Milestone status: VERIFY
Wave: 3
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 1 of 1

Moves

plan.transition

What it is

Objective: Apply the projection so that every canonical record exists on GitHub exactly once, adopt the 19 records that already exist rather than duplicating them, and record the run as evidence.
Why: The gate that follows is only honest against a projection that has been applied. This is the one outward-facing mutation in the milestone: it creates roughly 172 public issues, and it must be a confirmed act with a dry run read first, not a side effect of any other issue.
Now: Measured 2026-10-08 on master 4090b2b8ae: the backfill has been applied. scripts/github-sync --check finds 242 of 257 issues and 23 of 24 milestones in sync; 12 issues and 1 milestone, all records written since, are not on GitHub. .ai/repo/ci/github-drift-baseline.txt still reads missing 192 and adopt 19 as written on 2026-09-10, so the ceiling was never lowered with the run, and no evidence records the run that applied the projection. Still open: project the records that are missing, lower the baseline in the same commit, and record the run.
Wanted: `scripts/github-sync --check` exits 0. Every canonical record holds the number it was projected onto. The run is recorded as evidence with its date and the count it created.
Done when: unknown: the record declares no `completion`
Risk: High and outward-facing. It publishes 172 issues to a public repository in one run and cannot be undone cheaply. It requires the operator's explicit confirmation and must run after I1401, or the pagination ceiling will corrupt it.

Acceptance

The dry run is read and its counts agree with the check before anything is applied
The 19 existing issues are adopted, not duplicated, and the issue count after the run equals the canonical count
scripts/github-sync --check exits 0 immediately after the run
The gate's baseline is lowered to zero in the same commit, so the backlog cannot silently return
The run is recorded as evidence naming the date, the counts and the commit

Validation: scripts/github-sync --planscripts/github-sync --check
Evidence required: backfill_applied
Evidence present: backfill_applied

Scope

Touches: .ai/repo/project.ai/repo/ci/github-drift-baseline.txt
Not: Any change to the adapter, which I1401 and I1402 ownClosing or reopening a GitHub issue by hand
Depends on: I1401 I1402 I1404
Priority: p0
Profile: implementation
Parallel safe: false
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-09-09
Updated: 2026-10-14T19:49:23Z
Started: 2026-10-14T19:48:10Z
Verified: 2026-10-14T19:48:46Z
Completed: 2026-10-14T19:49:23Z

Synchronisation

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.