shape-doctor.py: the placement row asks a leg's top-level single-repository.yaml the staying-single record's question by its name alone, so a file that declares kind: release-config is told it records that the repository stays single, on every run of a project adopted before #617 #691

Goal: the doctor asks a leg's single-repository.yaml the record's question only when the file IS the record, as adopt-project.py plan does.

Filed by lane openRepoShape-3 on Brett Heap's word of 2026-10-16T12:24:41Z ("give #460 to lane 3").

Size: S. Lands after: #655, which changes the same row (audit_leg, answered_questions).

What happens (in-process probe on main d4a7fab: a code leg holding single-repository.yaml with kind: release-config and src/main.c, run through the doctor's audit_leg):

• With no answered_paths: row, the row asks the record's question:
  • it says review_required: 1, rule: ambiguous-single-repository-record and classified_as: null;
  • the question reads "This file records that the repository stays a single repository ... Drop it (drop, the default ...";
  • --placement-plan writes the same entry, because placement_plan_text builds from the row.
• plan asks the general top-level-YAML question of the same file, because ask_about_a_record_only reads its kind:.
• adopt-project.py, shape-doctor.py, validate-manifest.py: execute records the plan's answers under answered_paths: and a moved submodule names its row, so an answered examples/ is not asked again and a deliberate move names no plan (#525) #617 (59e5a07) narrows it but does not close it.
  • execute now records the answer under answered_paths:, and the row then lists the file as answered. The probe's answered_path_record writes - path: "single-repository.yaml" leg: code.
  • That answered entry still carries rule: ambiguous-single-repository-record.
  • Every project adopted before adopt-project.py, shape-doctor.py, validate-manifest.py: execute records the plan's answers under answered_paths: and a moved submodule names its row, so an answered examples/ is not asked again and a deliberate move names no plan (#525) #617, and any such file a leg gains later, is asked the record's question on every run.
• The verdict and exit code do not move, since the row is a note.

Where it is (d4a7fab):

• shape-doctor.py:6066: walked = adopt.walk(policy, kept), inside audit_leg (:5978-6085).
• adopt-project.py:1701-1734: RECORD_RULE and ask_about_a_record_only.
• scripts/shape_advisory.py:646: read_record, which takes a path or a Tree.
• contracts/path-classification.yaml:443-446: the comment saying the doctor reads the leg's copy as a question, by name.

The change:

• In audit_leg, where the walk gave a top-level single-repository.yaml the record rule, call shape_advisory.read_record(<mount>). Unless the result is RECORD_SILENCES, reclassify that entry with policy.classify_file(path, skip=(adopt.RECORD_RULE,)), as ask_about_a_record_only does.
• An answered entry then names the general rule.
• Change the comment at path-classification.yaml:443-446 to match.
• Change only the doctor. adopt-project.py is held by lane 1's claims.

Tests:

• tests/test_adopt_single_repository_record.py, beside test_the_doctor_reads_a_legs_copy_as_a_question_and_not_misplaced:
  • a leg file declaring release-config gets the general question;
  • one declaring single-repository-record keeps the record's question and its default.
• tests/test_doctor_recorded_answers.py: an answered file that is not the record names the general rule.

From #460, #460 (comment) (L12, L2-48).

🤖 Generated with Claude Code