Skip to content

Emit opt-in catalog location notices after CLI saves - #368

Open
Brian Krabach (bkrabach) wants to merge 1 commit into
mainfrom
cli/catalog-location-notices-20261003
Open

Brian Krabach (bkrabach) wants to merge 1 commit into
mainfrom
cli/catalog-location-notices-20261003

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

Successful CLI native saves and renames did not announce their changed locations to the running catalog. The opt-in environment variable now emits the existing bounded location-only notice after canonical save success.

SessionStore save, new, transcript, metadata, update and rename wrappers are covered. Publication uses a validated private directory descriptor, a unique mode-0600 file, fsync, atomic coalescing and directory fsync. Notice failure cannot veto canonical save. No process activation, provider call or history watcher is added.

Validation: 43 source and 43 independent installed checks with zero skips. All 103 Python runtime files match source, wheel and installed package. Actual installed CLI save and rename plus the installed catalog qualified new discovery, five coalesced updates, one metadata read, native transcript preservation and failed inbox delivery. Foundation qualification revision is 64d9b8086094b1da25924650509a6df4ca5b1834.

Physical CLI deletion remains separately reviewed. Configured native-owner lifecycle proofs stay separate from location hints; this patch does not create deletion authority. No live CLI reinstall, browser/device acceptance, merge or deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant