Skip to content
Cockpit0.29.0
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

I0008

Project the model to GitHub milestones and issues

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
M000
Milestone status
DONE
Wave
5
Waiting on
none
Holds back
I0011
Behind it in all
3
Evidence
2 of 2

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0008

majordomus plan verify I0008

majordomus plan done I0008

What it is

Objective
Create and update GitHub milestones and issues from the canonical model, report drift instead of overwriting human edits, and keep every network call out of the tool itself.
Why
GitHub is where collaboration happens, so it must show the plan. It is not where the plan lives, so it must never be the thing that defines it.
Now
The repository had no GitHub issues or milestones at all.
Wanted
scripts/github-sync renders the projection from majordomus plan body, creates what is missing, updates what changed, and reports what a human has edited.
Done when
unknown: the record declares no `completion`
Risk
A sync that overwrites a human comment thread would make GitHub hostile to use.

Acceptance

  • The adapter runs offline against a fixture and produces the exact payload it would post
  • A managed issue whose body differs from the projection is reported as drift, not overwritten
  • A closed issue whose canonical status is not DONE is reported
  • The tool itself contains no network client
Validation
bash test/run.sh 45_github_projectionscripts/github-sync --plan
Evidence required
projection_testgithub
Evidence present
projection_testgithub

Scope

Touches
scripts/github-sync
Not
Writing GitHub state back into the canonical filesAny network call inside bin, lib, share or test
Depends on
I0005
Priority
p1
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04T04:08:51Z
Started
2026-09-04T03:13:04Z
Verified
2026-09-04T03:13:05Z
Completed
2026-09-04T04:08:51Z

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.