44r0n7
a36c02bbf7
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.
13 lines
873 B
Markdown
13 lines
873 B
Markdown
# Repository Instructions
|
|
|
|
## Project Map
|
|
- Read `PROJECT_MAP.md` before doing substantive work in this repo.
|
|
- 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.
|