One repository may hold both memory scopes, and the gates now know it

[spscream]

Reported from the fleet checkout: run commit refused to commit fifteen changed files in the private scope, each named as not changed: wrong path, or the edit was lost, while git status in the store listed every one of them.

The layout

A project that cannot commit notes next to its code — a fork kept for upstream PRs — points public_repo and private_repo at the same repository. The scopes do not collide: they sit at public/projects/<key> and private/projects/<key> inside it. store, workplace and link all wire it and all report success. Only the checks did not cover it.

The cause

FLOPPY_PRIVATE_STORE was derived by asking whether the private scope's repository differs from the memory store — identity, where the question is containment. The memory scan reaches what lies under FLOPPY_MEMORY_REAL; a sibling prefix in the same repository is not under it. So the variable was blanked, scan_scope returned on its first line, and every file in the scope wore the message for a typo.

_derive_common next to it has always used containment, and says so in its own comment: common/shared normally resolves into the memory's own store.

What is in the change

lib-config.sh	containment instead of identity
wrap-commit.sh	one repository is one commit — before this, both scopes in one clone meant two commits with the same message, two pushes, and two sections naming the same path
wrap-guard.sh	a scope no store covers is told so, with the path it resolves to; the scan returns silently on an empty store, so a future blanking would wear the typo message again
memory-lint.sh	[[ -n "\$x" ]] in a note is no longer read as a link — a hard error that took check and the commit with it, inline or fenced

Verification

Each half was reproduced before the fix and pinned after it:

• tests/test-external-memory.sh — the one-repository shape end to end: both links wired, FLOPPY_PRIVATE_STORE equal to the memory store, guard accepting a private note, and a commit spanning both scopes landing as one commit with both paths in the remote. Plus the half-wired shape, asserting the honest message.
• tests/test-memory-lint.sh — a note quoting a bash condition passes, and the positive control that a dangling [[slug]] still fails.

Suite: 23 files, 1018 assertions (+17), 0 failed on /bin/bash.

Released as 0.25.1; the shim is untouched, so the changelog answers "Refresh .floppy/run?" with no.

Not reproduced, and not changed: the reporter also saw git status --porcelain collapsing a new scope directory into one ?? line. With the store ignoring the wiring link the way workplace leaves it (ignore_wiring_link), that line does not appear; scan_scope already passes --untracked-files=all.