Subcategory: Template fidelity
Current score: 9/10 → Target: 10/10
The repo is synced to the Rhiza template at v1.2.0:
.rhiza/template.lock → ref: v1.2.0 (synced_at 2026-07-16).rhiza/template.yml → ref: "v1.2.0"
But the locally-owned CLAUDE.md still advertises the old version:
CLAUDE.md:10 → "...Rhiza-managed repository (template v1.1.2)."
This is stale documentation drift in a locally-owned file. Anyone reading CLAUDE.md
(including future agent sessions) is told the wrong template baseline, which can lead to
incorrect assumptions about which files/targets are available upstream.
Where to change
src/config are fine; only CLAUDE.md:10 needs the version string updated from
v1.1.2 to v1.2.0 (and ideally kept in sync with .rhiza/template.lock ref: on
every future sync).
Done when
CLAUDE.md states template v1.2.0 (matching .rhiza/template.lock and
.rhiza/template.yml), and no other locally-owned doc references the stale v1.1.2.
Subcategory: Template fidelity
Current score: 9/10 → Target: 10/10
The repo is synced to the Rhiza template at
v1.2.0:.rhiza/template.lock→ref: v1.2.0(synced_at 2026-07-16).rhiza/template.yml→ref: "v1.2.0"But the locally-owned
CLAUDE.mdstill advertises the old version:CLAUDE.md:10→ "...Rhiza-managed repository (templatev1.1.2)."This is stale documentation drift in a locally-owned file. Anyone reading
CLAUDE.md(including future agent sessions) is told the wrong template baseline, which can lead to
incorrect assumptions about which files/targets are available upstream.
Where to change
src/config are fine; onlyCLAUDE.md:10needs the version string updated fromv1.1.2tov1.2.0(and ideally kept in sync with.rhiza/template.lockref:onevery future sync).
Done when
CLAUDE.mdstates templatev1.2.0(matching.rhiza/template.lockand.rhiza/template.yml), and no other locally-owned doc references the stalev1.1.2.