§7.6 landed — export + catalog RC ✓ landed 2026-07-21
Evergreen: catalog-expert-review-remediation §7.6.
Resolves f-close-out-residuals. The close-out surfaced that the planned residue
was mis-scoped twice over, and drove out four genuine root-cause bugs before the RC could cut.
1 — the residue was a double misdiagnosis
The plan carried the residue as "6 *_strain_gauge→*_strain_gage US-spelling renames."
Both halves were wrong:
- Spelling was a red herring.
american_spelling_check(NC-17) is an advisory audit — it never quarantines. Andgaugeis the standard American spelling (Merriam-Webster headword; the IMAS DD itself writes "strain rosette gauge"). Thebreamelibrary mapsgauge→gage, a niche variant. Chasing it was incorrect. - The names are correct. Verified 1:1 against the DD:
operational_instrumentation/sensor/directionand.../direction_second(a strain rosette gauge's two measurement-direction unit vectors), each with x/y/z components → 6 names, structurally identical to 20+ accepted siblings (x_direction_unit_vector_of_camera, …). Not a pipeline error. - The real defect: 5 of the 6 documentation bodies contained unfilled/bracketed
placeholder text (e.g.
[x component of the second measurement-direction unit vector]) that tripsplaceholder_check— a critical, quarantining audit → excluded from export.
2 — docs fixed, zero renames
Authored clean, bracket-free documentation for the 5 affected names, modelled on the one already-valid
sibling, applied through the pipeline via sn edit --docs (each scored ≈0.90, above the 0.85 bar).
All six now name=accepted · docs=accepted · validation=valid. A deterministic
drain_validation pass cleared the stale placeholder-era quarantines (0 re-quarantined).
The names themselves were never touched.
3 — four root-cause fixes driven out en route
| Fix | Commit | What was broken |
|---|---|---|
| NC-17 spelling allowlist | imas-codex 27ac45ee |
gauge/gauged/gauges exempted — valid US spelling wrongly flagged by breame. +regression test. |
| DD-source re-seed | imas-codex 3bdf37d5 |
_pin_dd_source_snapshots raised "no exact dd_version" before consulting the existing node, so sn run --focus/--edits crashed re-seeding an already-pinned source. Now reuses the stored snapshot. +3 tests. |
| Export deprecation-stub query | imas-codex a0b7c1ca |
ORDER BY old.id after an aggregation was a Neo4j SyntaxError that aborted every export. Ordered by projected record.id. |
| ISN-error quarantine severity | imas-codex 426132e8 |
_is_quarantined treated all ISN [semantic]/[structural] issues as advisory; ISN's publish gate hard-fails on ERROR-level ones. A bare coordinate (geometric quantity lacking a qualifier) stayed valid and blocked the release. ERROR-level issues now quarantine. +3 tests. |
ISN grammar carried a matching correction: the strain_gauge/strain_gauge_sensor
locus tokens were briefly renamed to gage and then restored (ISN 73126e5); imas-codex
re-pinned across the churn.
4 — catalog RC cut
Released v0.2.0rc63 → origin (ISNC commit 007a39f1).
Export: 1858 names of 1909 candidates (3 below-score, 5 unreviewed, 6 grammar-parse
excluded in RC mode, 1 bare coordinate quarantined). All four export gates PASS
(graph_tests, score_thresholds, cross_field_consistency, divergence_detection); staging validation clean.
The rc62→rc63 delta (≈2148→1858) is expected RC churn — superseded predecessors from this plan's own
remediation renames drop out, new names land.
5 — follow-on
One convention-level question was logged, not a defect:
f-ordinal-carrier-readability — names like
x_first_measurement_direction_unit_vector_of_strain_gauge read awkwardly because the
geometry carrier leads with an ordinal under the bare component-prefix grammar rule. The names are
canonical and DD-faithful; whether ordinal-led carriers should be re-phrased is a grammar review, not
an RC blocker.