feat: preserve full-text approval through writes and recovery

[seonghobae]

September 6 source-inventory prerequisite checkpoint

Current OPEN Draft head 6779fc40c71eccb03b0784cee6c3b5c14fb6e25a preserves 22a29c1 over exact parent #38 e2c3a9fbbe36f44525833d4a94e164c6891a0f94. This is a baseline-only update: runtime remains e1407d64e67be3556088c36d334427b7de103378 and does not yet include the new #9 inventory/revision/blank-key source. Fresh exact-head 258 tests / 41 unfiltered suites, including seven doctests, fmt/CI/diff and source-identity checks pass.

The existing #9 owner was normally pushed at 51c7df6d03f072449422fd58ca24b2f9d6026f07 with 47 tests / 10 suites. It preserves nonbibliographic metadata and unresolved ancestry, and rejects blank identity before page accumulation. A genuine earlier inventory executable reads 8,326 records = 3,715 unchanged proposals + 4,611 other records, retaining the four audited pending sources. Owner evidence and integration requirements.

Required next work is consumer restoration/identity partition/pending-ancestry validation before worksheet and direct evaluation/duplicate/write verifiers, with explicit bibliographic-only versus full-library completion. Neither tests nor empty pending keys grant approval. Capture/report bindings must reject incompatible scope; no capture rewrite or default-empty legacy inventory. New Visual Inspection was attempted but the Mac is locked, so no fresh screenshot is claimed. No model, Zotero mutation, approval, protected merge or closure. Earlier checkpoints below are historical.

September 6 live/visual audit and deadline integration checkpoint

Current OPEN Draft head: 22a29c1cfc0918fa34287f3bffe7f400e97f4a0f, normally pushed after preserving remote ec1435379e5fb29fbd7842137a2003d8f3363655 and parent #38 e2c3a9fbbe36f44525833d4a94e164c6891a0f94. Runtime remains e1407d64e67be3556088c36d334427b7de103378; this audit increment changes documentation only. The follow-up baseline records successful normal pushes, exact PR-body/reply readbacks and mandatory Visual Inspection, retaining the original live audit at 55b1d91.

Fresh locked Rust 1.98.0 run at this head: 258 tests / 41 unfiltered suites, including seven doctests; formatting, existing CI contract, diff checks and source-identity comparison pass. Earlier strict source verification and unchanged coverage at e1407d6 are separately recorded: 415/415 functions, 4,465/4,465 normalized regions, 762/762 normalized branches; raw LLVM 5,041/5,115 lines, 7,281/7,438 regions and 707/762 branches are not 100%. No fresh coverage run is implied by this documentation-only increment.

The actual Local API and visual audit uses the isolated #9 owner executable, not this root runtime. It observes 8,326 records, 3,715 bibliographic proposals and a native 3,719-top-level selection. Complete scope reconciliation finds three standalone PDFs and one standalone note outside the worksheet. They remain unresolved; do not call the bibliographic-only denominator full-library completion. Retraction warning is visually verified, but the later one-record retracted view is accessibility evidence only because captured frames remained stale. No raw metadata or screenshots are committed.

The GitHub cooldown audit recovered normally at 11:07 UTC: 33 open, 32 Draft, 36 unresolved and no current-head approval in the latest 30 reviews per PR (older #6 history outside that window). The #9 item-revision guard f856640 is still awaiting forward propagation, and the new pending-scope runtime gate is unimplemented. No model call, Zotero mutation, authority issuance, self-approval, protected merge or closure occurred. Historical details below retain their original heads.

Summary

Progress on #8; this does not close the campaign. Stacked on #38 at 8e057652ee7784b373beeeec865d80dd3db773be, preserving its entire delta.

• Require the complete capture-bound golden set, explicit reviewed metadata replacements and mode. Reuse private preparation of the existing golden/write validation bodies; every local check precedes both real authority verifiers.
• Keep an opaque full-text plan and the same versioned complete-scope commitment on execution, rollback, retry and delayed rollback reconciliation. No executable legacy-plan projection or free inverse-operation mixing.
• Refuse unknown original-write state, dry-run and empty inverse work before rollback I/O. Preserve untouched recovery work; a still-indeterminate reconciliation cannot retry.
• Keep typed-only admission. Serialize owner-only audit evidence without restoring executable authority; omit source text and authority inputs from write receipts.
• Update PRD/TRD/Proposed ADR 0007/architecture guidance/UML/doctoring/Gap and the experiment plan. No new dependency, transport, service, credential or live-write CLI.

Previous local admission/recovery evidence

Runtime bdf55bfb95b3e688e9ec58eda2785d17ed853b4e:

• Locked Rust 1.98.0 workspace 252 tests / 41 unfiltered suites, including six doctests; baseline 240/41.
• Nine new unit tests cover invalid later input, capture/proposal/label mismatches, both verifiers and modes, substituted scope under old authority, dry-run, stale preflight, partial writes, conditional restoration, rollback retry, and unchanged/restored/unknown/failed delayed observations.
• Three additional compile-fail examples reject persisted plan admission, legacy-plan projection and mixed rollback operations.
• Strict all-target Clippy, fmt, warnings-denied rustdoc, CI contract, release build and diff checks pass.
• Existing coverage gate: 402/402 functions, 4,448/4,448 source-normalized regions, 750/750 normalized branch outcomes. Raw LLVM: 4,924/5,023 lines, 7,113/7,298 regions, 693/750 branches, not 100%. Thresholds and exclusions unchanged.

Committed RED/GREEN: admission 47d4e890e3bf29a3f7596d7a9a0a25f780b59e8f → d36dad824f6d78c76cf3b5a009dee15f09e6b02f; recovery 79e1c222267b6b93ce6506110e5e8ac704dc0a75 → 425fb8c46661c3f90646bb562922428b046010a9; missing branch cases bdf55bf. Failed attempts remain in history.

September 6 owner-discovery follow-up

Documentation 3acd93f512e7e9e3e66c22dfef02f18c4df1ff6a and follow-up 789637f6a54373c3176e42dda78b1075937fd273 add exact-default-source audits for kaefa, aFIPC and nonnest2, plus PRD/TRD/Proposed ADR 0006/research-register/Gap consequences. They are adjacent statistical evidence candidates, not adopted ontology generators. GitHub-release-bearing candidates remain seven (7/30); CRAN publication remains unverified after retrieval errors. No R execution, source copying, new dependency or private-paper read occurred.

The documentation revision passed a fresh locked Rust 1.98.0 workspace run: 252 tests / 41 unfiltered suites, six doctests, plus the CI contract, fmt, diff and unique-30-candidate checks. Runtime/Cargo/scripts are unchanged from the previously verified bdf55bf; the earlier coverage numbers are not a new coverage run.

Existing kaefa issue #48 carries paired-observation/missingness/unavailable-result acceptance requirements. Existing CO release PR #1030 carries immutable artifact/schema/protected-provenance/deployed-version requirements. That release PR remains Draft at audited head 6c25848728a3333365454a2c74a607d576abe4c9; other registries/deployments are unverified, not proven absent. No duplicate writer or release implementation was created.

September 6 original-write inspection follow-up

Runtime dcc36310394c68fca74251ae85fe72d942be32ba and documentation 77e8dce8126d1824f192ccc992c117b177e1bd12 preserve the exact request for an indeterminate original write, including its actual library precondition after earlier writes. One read-only observation borrows the unchanged opaque original receipt, keeping earlier inverse work, failed/untouched items and complete scope commitment. Matching, foreign, malformed or failed later observations never clear uncertainty or grant retry/rollback authority. No classifier, replay engine, new executor, dependency or live call was added.

• Preserved RED e300eb8: missing observation API at both new test calls.
• Fresh runtime baseline 252/41; candidate 255 tests / 41 unfiltered suites, including seven doctests; eleven focused functions pass.
• Strict all-target Clippy, fmt, warnings-denied rustdoc, CI contract, release build and diff checks pass.
• Existing coverage gate: 404/404 functions, 4,448/4,448 normalized regions, 752/752 normalized branches.
• Raw LLVM: 4,971/5,045 lines, 7,164/7,321 regions, 697/752 branches; not 100%. Existing thresholds, normalization and exclusions unchanged.
• PRD/TRD/Proposed ADR 0007/DDD guidance/UML/Gap/doctoring record inspection versus authority and official Zotero token limits. The documented memory-only token is redundant for versioned writes; no retry token implementation was added.

This closes only the missing-attempt-evidence and inspection portion. Governed original-write resolution and durable recovery remain unfinished. Capability stays 28; source audits 30/76 and decisions/independent approvals 0/3,715 each are unchanged. Earlier sections are historical evidence, not the current runtime.

Previous prerequisite coordination checkpoint

Documentation head b645d6acc9396aabe05294dc617fce5b70bd3223 records the explicitly handed-off Source Observation repair in PR #6 at 331f8edcd7cebb1719e5cea3187f3848ce7b9e71, without copying or adopting unprotected supplier source. Its exact-head doctoring retains the executed UNIQUE collision/framing RED, minimal optional-evidence/v2 fix and observed prerequisite failures/repairs. The existing owner performed a read-only scoped review and reported no additional blocking source finding; this is not GitHub approval or a separate execution of tests.

This #39 documentation-only head independently passes 255 tests / 41 unfiltered suites, including seven doctests, CI contract, fmt and diff checks. Its crates, Cargo files and scripts are unchanged from 77e8dce8126d1824f192ccc992c117b177e1bd12; the original-write runtime remains dcc36310394c68fca74251ae85fe72d942be32ba. No fresh #39 coverage run is claimed for this documentation change. Source Observation verification is supplier evidence, not this lane's runtime behavior, protected integration or Zotero authority.

Latest relationship-owner discovery checkpoint

Documentation head ec1435379e5fb29fbd7842137a2003d8f3363655 advances bounded source audits 30/76 → 33/76, leaving 43 repositories. Protected-default ThreadWeave, mightyETL and scopeweave inspections retain exact source, complete tracked-file trees, package/license limits and GitHub release/tag observations. GitHub releases with resolved source remain 7/33; ThreadWeave PyPI 0.1.0 is a separate registry observation, not current-source artifact provenance or verified adoption.

The inventory, PRD/TRD, Proposed ADR 0006, Context Map and Ubiquitous Language distinguish message ancestry, raw CDC producer capability and work dependencies from semantic authority. The PostgreSQL DDL documentation mismatch was handed to existing mightyETL issue #159 and its body independently reread; it is an open owner repair, not a fixed live incident.

• Three existing scopeweave unit scripts passed with Node v24.19.0; no supplier Java/Python tests, service, private data, browser or model was exercised.
• Both documentation commits passed fresh explicit Rust 1.98.0 workspace runs: 255 tests / 41 unfiltered suites, including seven doctests. Final fmt, CI contract and diff checks pass. Unique inventory count is 33.
• Initial unqualified Cargo failed before tests because inherited RUSTUP_TOOLCHAIN=stable selected installed 1.97.1; retain that log and use cargo +1.98.0. No toolchain installation, project-baseline change or shared environment edit.
• Crates, Cargo files and scripts are unchanged from b645d6acc9396aabe05294dc617fce5b70bd3223. No new coverage run, runtime dependency, utility repository, Zotero call, paper decision or authority issuer.

Earlier sections retain historical source/audit denominators. The existing hourly automation now follows these current coordinates and owner findings, preserving quiet-on-unchanged behavior. This source discovery does not complete the research campaign.

Explicit remaining gates

Actual paper decisions and independently approved labels remain 0/3,715 each; source audit is now 33/76; 43 repository sources remain. No private capture was opened, model requested, authority issued or Zotero record written in this increment.

Independent deployed authority/revocation policy, durable recovery admission after restart, delayed unknown-original-write reconciliation, released owner contracts and approved live write/rollback remain incomplete. Receipt results are per-attempt; earlier receipts remain necessary. Local GREEN is not hosted GREEN, review approval, protected merge or publication. Keep Draft until prerequisite and protected gates permit normal progression; no bypass, force push, retarget or predecessor closure.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Fresh parent-lineage coordination finding — read-only; no #39 source/base/head mutation performed here.

PR #38 has advanced after this PR was established. Live #38 is now e2c3a9fbbe36f44525833d4a94e164c6891a0f94 on base 2688b508e36ac1be15c15717566a0bc165ab962d. Its new head e2c3a9fb... is an ordinary merge successor with parents 8e057652ee7784b373beeeec865d80dd3db773be and 2688b508e36ac1be15c15717566a0bc165ab962d (merge(research): inherit bounded metadata reads into PR #38). PR #39 still points to the same parent branch at old base SHA 8e057652..., head ec1435379e5fb29fbd7842137a2003d8f3363655, and GitHub currently reports it non-mergeable.

Treat this as a wrong-base/intervening-delta repair finding, not as a reason to close, retarget destructively, or discard either lineage. Root sole writer should first reread both exact heads and the 8e057652... -> e2c3a9fb... parent delta, then adopt/adapt every valid #38 change into #39 with an ordinary non-force restack/merge while preserving the complete #39 runtime/tests/fixtures/contracts/evidence. Re-run #39 exact-head Rust/docs verification after the resulting head changes; predecessor local evidence must remain historical rather than transferred as current GREEN.

I am not asserting that the conflict itself identifies a semantic defect, that hosted checks exist, or that protected acceptance changed. Keep #39 Draft/ADR Proposed and preserve the existing root single-writer boundary.

[seonghobae]

Coordination only; no #39 source/base/head write. The upstream research owner PR #9 advanced normally during this run to exact Draft head 51c7df6d03f072449422fd58ca24b2f9d6026f07 on unchanged Foundation base. Its current runtime lineage adds complete nonbibliographic metadata inventory + pending_source_item_keys, validates the previously audited three standalone PDFs + one standalone note against the real 8,326-record library, and adds blank-item-key fail-closed admission after the earlier item-revision guard. Current #39 remains 22a29c1cfc0918fa34287f3bffe7f400e97f4a0f on #38 e2c3a9fbbe36f44525833d4a94e164c6891a0f94, so the body’s f856640/unimplemented-pending-scope checkpoint is now predecessor metadata. Please adopt the complete verified #9 delta by ordinary forward propagation/restack when this sole-writer lane reaches it; do not transfer predecessor GREEN or collapse the four pending sources into the 3,715 bibliographic denominator. Separately, the existing #9 P1 tag-adjacency thread remains valid at 51c7df6...: independent tags must not synthesize a multiword rule phrase. This comment grants no approval and does not request retarget/force/closure.

[seonghobae]

Dependency note after fresh parent sweep: #39 is still mergeable on exact #38 e2c3a9fbbe36f44525833d4a94e164c6891a0f94, so there is no child-local conflict to repair yet. However #38 itself is now non-mergeable because #37 advanced to 9d72bbf02199dfc7b668bca33b891307f8278d7f after adopting repaired #36.

Keep #39's write-admission/recovery delta intact and do not independently pull #37/#36 fixes past its canonical parent. Wait for #38 to ordinary non-force adopt the repaired #37 successor; then ordinary non-force integrate that repaired #38 successor here and rerun exact-head verification. No predecessor GREEN/approval transfers across that cascade.