Skip to content

docs(config): clarify unreadable project scope fallback #934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeff-r2026 merged 1 commit into from
Oct 1, 2026
Merged

docs(config): clarify unreadable project scope fallback #934

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/designs/data-directory-layout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,8 +272,11 @@ partition on the next write command, so the workspace ends up with zero residue.
`contribute --scope user` (the user install's queue) and `import --from-mr
--output` (drafts only) do not write this project's queue, so they do not
migrate either.
Read-only commands (`status`, `recall`, …) keep using the double-read fallback
and never move data.
Read-only commands (`status`, `recall`, …) never move data. They can still read
a valid legacy project config through the double-read fallback, but an existing
unreadable project config is not treated as absent: scope resolution stops
with a config error instead of falling back to another project's or the user
scope (#899).
- `hook-dispatch` is excluded outright (via `TEAMAI_HOOK_SUBCOMMANDS`): it is a
high-frequency silent path and must never move 12 MB.
- `--dry-run` (the existing global flag) previews without writing.
Expand Down
Loading