Twinned from https://github.com/cfsh/ninefold/issues/639 by tools/beads/import_github.py's reconcile pass.
#549 added notes/office.md, which says of the office-tooling rule:
> tools/office/spawn_dev.py is the standing example; tools/office/README.md is the same rule written for a reader standing in that directory.
The link only goes one way. tools/office/README.md does not mention notes/office.md, and nothing else in the tree does either:
``` $ grep -rn "notes/office.md" --include=*.md --include=*.py . | grep -v "^./notes/office.md" (nothing) ```
CLAUDE.md and notes/README.md list it by description, so a reader arriving from the top finds it. A reader who arrives at tools/office/ — which is the entry point when you are actually touching the code — does not: that README sends them to cfsh/nf-office (runbooks/spawn-dev.md, DECISIONS.md) for the reasoning, and on a dev box that repo may not be checked out, whereas notes/office.md always is.
Not a correctness bug in either file; both were right when written, and notes/office.md is three hours old. It is the cheap half of a cross-reference that already exists in one direction.
Found while rebuilding #626 onto the main that #549, #553 and #603 had just landed on — so it is a discovery from an unrelated chunk. #626 already edits tools/office/README.md, and folding a doc pointer with nothing to do with --adopt into a PR that is CONVERGED and awaiting @aedanpope is scope creep on a PR trying to land.
tools/office/README.md:83 says *"See office/DECISIONS.md"* — no repo prefix, and the path is cfsh/nf-office's, not a directory in this repo. Same family: a pointer that resolves only if you already know where you are.
None.
No comments.