Project Notebook

Treat Git and the repository's Project Manifest as authoritative. Treat the remote notebook as scoped, derivative context that PJangler owns and can audit.

Work through PJangler

1. Resolve the repository explicitly when the current directory is ambiguous.
2. Inspect pj notebook status [repo] before assuming a healthy binding.
3. Use --json when another tool will consume the result. Check ok, symbolic error code, and next_actions; do not infer success from prose.
4. Keep reads and mutations project-scoped. Never call the notebook service directly or accept a result whose membership in the resolved binding is not proven.
5. Use pj notebook audit [repo] to diagnose Drift. Use pj notebook migrate [repo] for an owned repair plan, adding --apply for local changes and --live only when remote repair is intended.
6. Preserve repository files as the source of truth. Never overwrite Git content from notebook content.