scripts/shape_materialize.py and scripts/family.py: the helpers that ask a template's own YAML reader and validator about a manifest's values exist twice, once for project.yaml and once for family.yaml #925

Goal: one set of helpers asks a template's own YAML reader and validator about a manifest's values, for project.yaml and family.yaml alike, with no change in behaviour.

Filed by lane openRepoShape-3, from its triage of #459 at the v1.1.1 release commit 5017830. It is #459's line U022 (lane 5's line from #397, which was #470), one pull request's worth.

The manifest-misread helpers exist twice (U022)

State. scripts/family.py holds family_validator (:3127), _reading_in_words (:3163), the other two line helpers, _misread_rows, family_manifest_misreads, _sentences_of, family_manifest_invalid and refuse_unholdable_manifest (through :3350). scripts/shape_materialize.py holds their twins for project.yaml, from manifest_validator (:4781) to refuse_manifest_values (:5203). #470 holds the full table and was closed as moved to #459.

What happens. No behaviour is wrong; a fix to one copy is easily missed in the other, as #817 showed when it fixed shape_materialize.py's whole-manifest words and left family.py's (U119, filed separately).

Evidence. The lines above at 5017830.

Direction. Unify them. The unified helpers must keep every refusal code and word, ask before anything exists, load each validator from its template, and touch no shape copy.

Size: M.

Lane: openreposhape-3 (openRepoShape-3)