Document: current-status-manifest-v0_75-amendment-v0_1
Version: v0.1
Date: 2026-07-28
Recipe: Apply these splices to current-status-manifest-v0_74.md and save the result as current-status-manifest-v0_75.md (add-new-file sibling — never git mv; v0.74 stays a standing sibling, byte-for-byte untouched).
What v0.75 records: record hygiene only — no build work. (1) The v0.69-era "not merged to main" sentences that survive inside the v0.74 header status and Entries 113/114 are marked superseded in place (corrections-preserved: the sentences stay; markers are appended). The repo is ground truth, verified 2026-07-28: git merge-base --is-ancestor feat-companion-surface main returns true; main..feat-companion-surface is 0 commits. (2) The repo-verified current fronts are recorded: OL main 99f7f64 (2026-07-19), engine main 1aac815. (3) A new §5 residue names the absorption gap those fronts expose: OL and engine work landed between 2026-06-28 (v0.72's b107290 / 0b2c232) and 2026-07-19/28 that no §3 entry records — including the OL "Item 7a" claim/credit merge and the engine advance 0b2c232 → 1aac815. The gap is named, not filled; filling it needs the session records.
Replace:
# Loomworks Current-Status Manifest — v0.74
with:
# Loomworks Current-Status Manifest — v0.75
And Version: 0.74 → Version: 0.75 (date stays 2026-07-28).
Locate the v0.74 Status paragraph (begins "v0.74 (2026-07-28, later same session): the OVA reach-enforcement scoping arc RAN"). Append immediately after it:**
> v0.75 (2026-07-28): record hygiene — stale-text supersession markers and repo-verified fronts; no build work. A CC repo inspection (2026-07-28) confirmed the v0.69-era sentences still standing inside this header and Entries 113/114 — "living on feat-companion-surface (not on main)"; "no merge to main" — are false against the repo: feat-companion-surface is fully contained in OL main (git merge-base --is-ancestor true; main..feat-companion-surface = 0), as the v0.70 text above already records. The sentences are preserved with appended supersession markers (corrections-preserved), not deleted. Repo-verified current fronts: OL main 99f7f64 (2026-07-19, "Merge Item 7a into main: /claim standing→credit fall-through + admin claim_url"; origin in sync; 60 commits past 3f2fca8), engine main 1aac815 (origin in sync). Those fronts expose an absorption gap filed as a new §5 residue: no §3 entry records the OL Item 7a claim/credit arc or the engine advance 0b2c232 → 1aac815 (the window 2026-06-28 → 2026-07-19/28); v0.73/v0.74 cite 1aac815 only as the SHA their inspections read. The gap is named here, not filled — filling it is its own absorption pass from the session records. The add-side completion-record residue remains open (in progress this session). Otherwise carries v0.74 forward.
Both insertions land inside the long opening Status paragraph, in its v0.69-era passage (which follows the v0.70 merge text).
3a. Locate:
The mobile Companion surface is on `feat-companion-surface` at **`dac9fec`** (pushed), built on top of `8bd73f2`.
Append immediately after it:
**[Superseded (v0.75): both are on OL `main` since the `3f2fca8` merge — repo-verified 2026-07-28 (`merge-base --is-ancestor` true, `main..feat` = 0). Preserved as v0.69 trajectory.]**
3b. Locate (header occurrence only — NOT the changelog v0.69 entry, which is a historical description and stays unmarked):
**Two residues named (§5): the add-side arc has no completion record; the OL add-side + mobile-Companion work is preserved on the feat branch only — no merge to `main`.**
Append immediately after it:
**[Superseded in part (v0.75): the second residue was resolved by the v0.70 merge (see §5 resolved-residue record); the completion-record residue remains open. Preserved as v0.69 trajectory.]**
Locate (in Entry 113):
(2) The OL half is on `feat-companion-surface` only — not merged to `main` — now anchored by the `add-side-rework-ol-v0_1` tag so it survives any branch lifecycle.
Append immediately after it:
**[Residue (2) superseded (v0.75): merged to OL `main` at `3f2fca8` (v0.70), repo-verified 2026-07-28. Residue (1) remains open.]**
Locate (in Entry 114):
No tag (lives on the feat branch under the same not-yet-merged-to-`main` condition as the add-side OL work).
Append immediately after it:
**[Superseded (v0.75): on OL `main` since the `3f2fca8` merge (v0.70), repo-verified 2026-07-28.]**
Locate the §5 item beginning "OL Companion work — MERGED to main (2026-06-28). [RESOLVED]". Append to the end of that item's paragraph:
> Re-verified against the repo 2026-07-28: git merge-base --is-ancestor feat-companion-surface main true; main..feat-companion-surface = 0 commits; tag add-side-rework-ol-v0_1 present (annotated, at cbd1742 → commit 8bd73f2, confirmed in main). OL main has since advanced to 99f7f64 (2026-07-19; 60 commits past 3f2fca8) — see the v0.75 absorption-gap residue.
Insert as a new §5 item, immediately after the item amended in Splice 6:
> Absorption gap: OL and engine work landed 2026-06-28 → 2026-07-19/28 with no §3 entry (filed v0.75). The manifest's last recorded build fronts are v0.72's OL b107290 / engine 0b2c232 (2026-06-28). The repos' actual fronts (verified 2026-07-28) are OL main 99f7f64 (2026-07-19, "Merge Item 7a into main: /claim standing→credit fall-through + admin claim_url") and engine main 1aac815. Neither advance is absorbed: the OL Item 7a claim/credit arc appears nowhere in the manifest, and 1aac815 is cited (v0.73/v0.74) only as the SHA the inspections read, never as a recorded advance from 0b2c232. Engine test names at 1aac815 (e.g. CR-2026-124 open/close intents, CR-2026-129 recall truthfulness, CR-2026-137 find-files, CR-2026-154 supersession-aware answering) indicate the window carries multiple landed CRs. Owed: an absorption pass from the session records for that window — a proper pass, not a reconstruction from test names. Until it runs, treat §1's substrate-state SHAs for OL/engine as superseded by the fronts named here.
## Changelog, above the v0.74 entry)
- **v0.75** (2026-07-28): **Record hygiene — supersession markers on the v0.69-era "not merged" sentences (header status, Entries 113/114), repo-verified fronts recorded (OL `main` `99f7f64`, engine `main` `1aac815`), and the absorption gap for the 2026-06-28 → 2026-07-19/28 window filed as a §5 residue (OL Item 7a claim/credit arc + engine `0b2c232 → 1aac815`, no §3 entries).** No build work; no entry added; the gap is named, not filled. Corrections preserved — every superseded sentence stays in place with an appended marker. Otherwise carries v0.74 forward.
Update the footer version line to v0.75 — 2026-07-28. Tagline unchanged.
Version: all read v0.75; filename current-status-manifest-v0_75.md is a new sibling; v0.74 byte-identical, still present..md (this lineage is .md-only since v0.52).
DUNIN7 — Done In Seven LLC — Miami, Florida
Current-status manifest — v0.75 amendment instructions — v0.1 — 2026-07-28
Splice list to turn v0.74 into v0.75: supersession markers on the stale v0.69-era merge sentences, repo-verified fronts (OL 99f7f64, engine 1aac815), and the June→July absorption gap filed as a residue. Hygiene only; nothing absorbed, nothing built.