Skip to content

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

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.

BLOCKED wave 1 · p1 · implementation profile · parallel safe

Part of adopter-upgrades — An adopting repository survives a Majordomus upgrade, and what the tool vendors into it is adopter-neutral.

Blocked. This issue cannot start until I1980 is done. The status is derived from that, not declared.

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.

Current state

rules vendor update copies the package and its manifest only.

Desired state

The update names every skeleton key the new rules read and the adopter lacks, and doctor reports the same list until it is resolved.

Scope

  • lib/rules.sh
  • lib/doctor.sh
  • share/standard/majordomus
  • share/skeleton
  • docs
  • test/cases

Dependencies

Acceptance criteria

  • 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 validate
  • MJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>

Evidence required

  • vendor_update_names_missing_keys

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1983.yaml. Read it back with majordomus plan show I1983.

Searches the titles and descriptions of every page this site publishes.