Detailed wiki content repair: Operations
@@ -0,0 +1,21 @@
|
|||||||
|
# Operations
|
||||||
|
|
||||||
|
## Maintainer Workflow
|
||||||
|
|
||||||
|
- Use the `Stewardship Readiness Checklist` issue as the active work queue.
|
||||||
|
- Move work through `Triage`, `Provenance Review`, `First Verified Release`, and `Maintenance`.
|
||||||
|
- Keep README, changelog, setup notes, and wiki pages synchronized when behavior changes.
|
||||||
|
- Prefer small commits tied to a specific readiness item.
|
||||||
|
|
||||||
|
## Day-To-Day Checks
|
||||||
|
|
||||||
|
- Confirm the default branch still has all stewardship files and issue templates.
|
||||||
|
- Keep dependency manifests and generated files separated.
|
||||||
|
- Before flashing, confirm board target, port, power state, and recovery path.
|
||||||
|
- Update release notes whenever a verified command, build, or artifact changes.
|
||||||
|
|
||||||
|
## Project Inventory
|
||||||
|
|
||||||
|
- Project files beyond stewardship docs: 1193
|
||||||
|
- Top directories inspected: .cache, esp-idf, build, (root), src, sdcard, include, .cursor, lib, .vscode, test
|
||||||
|
- Key manifest signals: CMakeLists.txt, README files
|
||||||
|
|||||||
Reference in New Issue
Block a user