Clarify local Change Set access and recovery boundaries

[jerelvelarde]

Summary

The local developer guide currently calls Change Set application atomic and describes agent access in ways that can imply process isolation. Clarify that publication is recoverable but ordinary files can become visible in several steps, that workspace listing and scoped copies do not restrict an agent’s other tools, and that database files need an application-consistent backup and supported replacement procedure.

Document Core 0.7.2’s new-file apply defect before the workflow, label the repair and its added conformance cases as unreleased, and update the repair verification note to the final evidence for 37ffaac7. Preserve the distinction between a stable capability contract and a defect in its released implementation.

Dependency

This documentation change and its focused contract-test correction are based on fix/change-set-added-object-capture and depends on #90. Neither this PR nor #90 is a published Core release. No application code, protocol records, or published website articles change.

Validation

• Full documentation CI job passed locally: all 14 scripts/tests/docs-site.test.mjs policy tests, npm ci --prefix apps/docs, then npm test --prefix apps/docs: ESLint, Next route type generation, TypeScript, and a production build of all 111 static pages (Node 24.4.1).
• Checked the four changed generated HTML routes, the agent access-boundary anchor, and the issue, candidate PR, and SQLite backup links.
• git diff --check passed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
folderbase-docs	Ignored	Preview	Sep 15, 2026 12:34am UTC