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

I1208

Adding a provider is one file, removing one is one deletion, and both are executed rather than described

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
web-sign-in
Milestone status
PLANNED
Wave
6
Waiting on
I1202I1206
Holds back
none
Behind it in all
0
Evidence
0 of 3
In the waySubjectDetail
issueI1202I1202 is not DONE
issueI1206I1206 is not DONE

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 I1208

majordomus plan verify I1208

majordomus plan done I1208

What it is

Objective
Document how a provider is added and how one is struck, and make the documentation executable: a test that adds a synthetic provider object and asserts it appears in the sign-in offer, in the capability read, in the generated documentation and in the Cockpit with no other edit, and a test that removes one of the two shipped objects and asserts every one of those surfaces loses it.
Why
The operator has said the first two providers may both be struck once the audience is known. That is the operation this milestone must make cheap, and the only proof it is cheap is a test that performs it.
Now
Nothing is documented and nothing performs the lifecycle.
Wanted
The add and the remove are both proved by tests, and the documentation states the one-file operation because a test executes it.
Done when
unknown: the record declares no `completion`
Risk
The removal half is the half that is skipped, and it is the half the operator asked for.

Acceptance

  • A synthetic provider dropped into the directory appears on every applicable surface with no source edit, proved by a test
  • Removing a provider object removes it from every surface, and sessions pinned to that issuer are refused
  • The documentation names the file to write and the file to delete, and cites the tests that execute both
  • A rule states that a provider fact may not be stated outside its object, with a check CI executes
Validation
bash test/run.shcargo test --workspace --all-featuresmajordomus generate --check
Evidence required
add_provedremove_provedrule_enforced
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docssiteapps/majordomus-cli/teststest/cases.ai/repo/rules/project
Not
A migration path for sessions issued by a provider that has been struck, beyond revoking them
Depends on
I1202I1206
Priority
p1
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-08
Updated
2026-09-08
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

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.