docs: migrate indexed Qdrant stores to the native user service

[seathatflowsinourveins]

Scope

An indexed Qdrant container can pass SocratiCode searches while still lacking the catalog's native user-service lifecycle. Add a reviewed full-storage snapshot/restore recipe that preserves collections and aliases, verifies application readiness, and records lossless rollback boundaries. It reuses the existing official binary and user-unit/config examples; host application awaits the command-center ACK. The proposal now targets official1.19.2 from the indexed1.19.1 store, with1.19.1 retained as fallback.

• Base commit: c1300c15b42f1a6643f3dc4172f40c01d99abdcd
• Lane: lane:foundation
• Owned paths: recipes/qdrant-user-service-migration.md, its recipes/README.md link. Documentation hashes are registered in the branch's last commit; no install-plan, client configuration or runtime pin is changed.

SOTA sources

• Proposed qdrant/qdrant@v1.19.2, commit 016542aa5deb6c66380bb137badf73d54f742bde; official musl archive33015429B, SHA256 50b253243309ed0ae50a19f678f0d0adcc4f0b567b3bd2c5c0c7e02fa8404bb6 from release-assets API.

• Retained source/B fallback qdrant/qdrant@v1.19.1, commit 6ab21cac18ebb6f4ae29102c7f8f5cc11affd5de; official musl archive SHA256 70a40529e2ebe0a2787d574d3a2e28437cfe94f26f24fa419f6ac57b4ae817c9.

• Full-storage snapshot implementation, native CLI recovery, recovery staging, official snapshot docs.

• SocratiCode@f6191f0 watcher policy: require manual watcher mode and SOCRATICODE_AUTO_RESUME=off before connecting every owned acceptance process; startup off:56–65, startup update:304, metadata write:1657.

• systemd@v259 Type=simple, ExecStart reset, resource control, Nice.

• Existing repository references at the base: catalog Qdrant pin/archive:687–693 and user-service steps:750, examples/native-stack-qdrant.service.example, examples/qdrant.yaml.example.

• The CC adopted v1.19.2, published2026-10-05T14:16:50Z, with the relevant storage/recovery fixes. Host application still awaits the new-head ACK. No catalog or active host pin is changed. 1.19.1/B hash remains recorded.

• Linux process argv: repin the ordinary base unit to1.19.2 before recovery, inspect effective ExecStart before ordinary startup, then inspect the owned MainPID's actual argv without recovery flags. Removing the override must not expose the historical1.19.1 path in the linked example.

• Official snapshot compatibility permits same-minor target patch >= source patch:1.19.1→1.19.2 supported in source. Target CLI recovery and target staging retained; native restore/version/inventory/search/restart remainUNRUN.

Review findings fixed: existing background work drains before snapshot, and each owned acceptance connection uses startup-off plus manual watcher mode. The ordinary base unit explicitly selects1.19.2 before recovery and is checked before ordinary startup and against the running process's argv afterward. Catalog citations point to Qdrant at the declared base. No live config or transport changed by this documentation refresh.

Evidence-class table

Claim	Evidence class	Command / receipt
Full-storage snapshot/user-service migration and rollback procedure	source_review	Pinned upstream code/docs above; no migration executed
Existing LM5 owned full index and expected-file search	local_integration	Retained private co-op native receipts:9089files/134719chunks, graph1824files/611edges, unfiltered docs/lanes.md result2
Publication integrity and registry consistency	structural_validation	scripts/validate.py exit0; no provider/GPU execution
Organic BEFORE counts	source_review (retained native census; not independently recounted)	Private census:Claude0 MCP calls in2026-10-05T05:47:50Z–2026-10-06T05:47:50Z from Loki; Codex0 in2026-10-05T05:55:38Z–2026-10-06T05:55:38Z from native completed MCP events
Organic AFTER	source_review	null/no complete post-migration window:the native user-service migration is unexecuted; requested acceptance calls are excluded

Local commands run

python3 scripts/validate.py
exit1 initially: changed recipes/README.md hash/byte count needed registration

host_receipts.register_file(..., recipes/README.md)
host_receipts.register_file(..., recipes/qdrant-user-service-migration.md)
python3 scripts/component_matrix.py --write
python3 scripts/new_host_grand_list.py --write
all exit0

nice -n19 ionice -c3 python3 scripts/validate.py
exit0:69components,10316hashed_files,4profiles,212receipts
Integrity and scope checks only; no live provider or GPU execution.

git diff --check
exit0

Decision record

The deployment form/pin already belongs to the architecture catalog. Patch selection and install-plan/dated-decision changes remain with the command center and their owner. The private host proposal renders the existing unit/config and one-time recovery drop-in; none is applied before ACK.

Host evidence

No new/changed file under evidence/hosts. Existing private host integration is not a native user-service acceptance result. Snapshot creation, .2 download/checksum execution, native restore/version/inventory, restart/retrieval and post-switch organic use remain unrun/pending.

Checklist

• No GitHub Actions changes.
• No credential values or active client configuration included.
• No new billing/hosting surface.
• Peer-owned untracked files preserved; superseded A17 drafts remain uncommitted.
• Evidence registry committed last.
• Co-op GPT first-pass review and command-center ACK before host application.

Landing path — 2026-10-07

The co-op micro-checks exact head 41d39dc7a0b35b15e98be4a9d769b91a7ae7463c, followed by the command center's exact-head ACK before any host migration. CC item143150Z requires that order; the older GPT ACK_AFTER on7c46510b is not the required ACK. The command center assigns this draft to 5f's remaining foundation queue after the critical-path order in CC item002346Z. The exact landing cue is requested in lane Q22 and remains pending; no queued/ACKed/host-accepted claim is made. Rebase only once on the actual landing cue under the hot-file protocol; 5f lands, this lane never merges.

J783b review fixes and CI boundary

All three findings from the GPT ACK_AFTER at45ada810 are addressed on the current base: rollback uses disable --now plus inactive/disabled readback before the rollback service, readiness/inventory/known-answer checks precede writers; storage/WAL and interrupted/repeated-recovery limits are explicitly PENDING with closure criteria and no unauthorized partial-target retry; the integrity row is structural_validation. No rebase, snapshot rehearsal or host migration.

Local checks at 41d39dc7a0b35b15e98be4a9d769b91a7ae7463c:45scoped documentation/citation tests passed(one skipped); validate.py passed69components/10316hashfiles/4profiles/212receipts; diffcheck passed. These establish artifact consistency, not upstream/native service acceptance. Registry commit is last.

CI at 41d39dc7a0b35b15e98be4a9d769b91a7ae7463c: UNKNOWN/not yet observed here, with mergeability DIRTY requiring the co-op's CI/landing-turn handling. Green hosted validate and exact-head CC ACK remain required before host application; local checks are not that ACK.

The actual OSV log at prior45ada810 reports GHSA-wq5f-xc86-pv6w (sharp0.35.4,fixed0.35.5) in the live application and frozen macOS pnpm locks. Both lock blobs match this PR's base and head, neither is a changed path, and both scans exited1: inherited repository-wide failure, not introduced by this recipe. #797 owns that advisory; this PR changes no lock, exception, workflow or dependency. The job checked pull-merge9d0560c5 while its run metadata names45ada810; no new-head all-green claim is inferred.

Dated consolidation limit — later CC ruling

From2026-10-07T01:47Z, CC review015759Z reports degraded ai-memory consolidation/auto-improve steady state through the correct cx/gpt-6.1-sol-max alias: roughly one in four to one in three calls succeeds pending the owner's free-connection pool decision. This is a dated NON-GATING operational limit, not this lane's new count. Model/alias/config remain unchanged. The23:47C2Xpass stands as a single successful run; no second smoke or canceled gateway count. The updated tracked record links the CC review/dispatch and qualified allowlisted-row observations; source-review data is not current independent health acceptance.

The earlier J783b/J800 review fix push was followed only to incorporate this subsequently discovered CC delivery. Both new exact heads pass the required local validator on their unchanged committed trees; hosted CI remains separately UNKNOWN here/mergeability handling stays co-op/5f. No rebase, history rewind, new PR or host change.