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

I1983

Upgrading the vendored rules reports or applies the policy and source keys those rules depend on

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
adopter-upgrades
Milestone status
ACTIVE
Wave
1
Waiting on
I1980
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI1980I1980 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 I1983

majordomus plan verify I1983

majordomus plan done I1983

What it is

Objective
When `rules vendor update` brings in rules that read policy keys or knowledge source classes the adopter's layer lacks, report each missing key with its skeleton default, or apply it, and have doctor name the gap.
Why
OSCILLA vendored the 0.12 rules (34f967a), including candidates-reviewed and the knowledge rules, but its .ai/repo/knowledge/sources.yaml still lacks the candidates, gap, critique, intent, domain and claim_page classes, and its policy lacks knowledge.candidates_max_files and candidate_max_age_minutes, all of which share/skeleton carries.
Now
rules vendor update copies the package and its manifest only.
Wanted
The update names every skeleton key the new rules read and the adopter lacks, and doctor reports the same list until it is resolved.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • Vendoring a newer package into a fixture with an older skeleton prints the missing keys with their defaults
  • doctor names the same missing keys
Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>
Evidence required
vendor_update_names_missing_keys
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
lib/rules.shlib/doctor.shshare/standard/majordomusshare/skeletondocstest/cases
Not
unknown: the record declares no `non_scope`
Depends on
I1980
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-10-04
Updated
2026-10-04
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.