Prepare the codebase for handover: docs, lint and contributor guide #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/handover-readiness"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Makes the repo easy to pick up for the next developer. No behaviour changes.
What changes
against the code and updated (five roles, free configuration parameters
instead of IO slots, no actor rules or flow versioning, exception mapping,
rate limits, rich text with embedded files, branch/PR/CI workflow).
codebase-map.md is rebuilt from the real layout, architecture.md is a real
overview, operations.md gains the backup/restore and dead-letter procedures.
Superseded ADRs get a one-line pointer; their bodies stay as history.
short recipes for adding an endpoint, a column or table, a flow change, a
notification, a frontend page and an npm package. Linked from the README.
allowed) with fixes for what it found: no setState inside effects, no ref
written during render, complete effect dependencies. The contract list no
longer lets a slow response for old filters overwrite newer results.
every PR; the image build waits for it.
unused SeededRoleIds class, "Cto" naming in demo data and tests.
Testing
Deployment
No migrations, no runtime changes beyond the contract list fix. Update the
stack as usual (optional).