Update tenant lifecycle tooling and retire docs/process
This commit is contained in:
@@ -18,4 +18,4 @@
|
||||
|
||||
## Operational Notes
|
||||
- Keep changes focused and reversible; document significant behavior shifts in the relevant `docs/*` or PRP files when surfaces change.
|
||||
- When tasks exceed scope, record follow-ups in `docs/process/todo/` rather than expanding the current patch set.
|
||||
- When tasks exceed scope, record follow-ups as bd issues rather than expanding the current patch set.
|
||||
|
||||
@@ -12,5 +12,5 @@
|
||||
## Operational Notes
|
||||
- Never change production infrastructure or data without explicit human approval.
|
||||
- For releases: use semantic version tags, generate a changelog, and ensure legal pages and migration notes are current.
|
||||
- For issue hygiene: import `docs/process/todo/` items into issues and avoid duplicates.
|
||||
- For issue hygiene: track follow-ups in bd issues and avoid duplicates by checking existing titles.
|
||||
- When ending a session, follow the Landing the Plane checklist in `AGENTS.md`.
|
||||
|
||||
Reference in New Issue
Block a user