docs: refresh preview update guidance and repo map

This documents the current preview apply contract, updates the project
map to match the live code paths, and adds the local scratchpad issue
tracking reminder to the workspace instructions.
This commit is contained in:
2026-03-31 17:23:13 -04:00
parent 7e95b7f95f
commit a36c02bbf7
3 changed files with 571 additions and 7 deletions
+5
View File
@@ -5,3 +5,8 @@
- Treat `PROJECT_MAP.md` as the primary orientation file for code structure, hot paths, feature ownership, and known issues.
- Update `PROJECT_MAP.md` when commands, modules, feature areas, persistence contracts, or major known issues change.
- After any meaningful structural or user-facing change, append a short one-line entry to the `PROJECT_MAP.md` change log.
## Local Testing Notes
- Periodically check the local-only `testing-notes.md` scratchpad during bug-fix work, especially before asking what to do next.
- When `testing-notes.md` contains unresolved items that belong in tracker form, convert them into Gitea issues and then rewrite the file back to its scratchpad prompt.
- Do not re-add `testing-notes.md` to git; it is intentionally local-only.