Self-dev customizations: integrate records into update flow with apply/repair status reporting
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Split from #32.\n\nUse persisted customization records during update/reload flows and report the outcome clearly.\n\n## Scope\n- load active customization records during update/install flows\n- surface record metadata to the agent/update logic\n- report per-customization outcome: applied cleanly, repaired automatically, needs review, disabled\n- run associated validation or smoke checks when available\n\n## Success criteria\n- update flow loads active customization records\n- agent/update path can inspect metadata for repair decisions\n- result summary clearly reports per-customization status\n- validation hooks run when configured and failures are surfaced\n- tests cover success and incompatible-customization cases\n\nBlocked by: #35, #36\nParent: #32
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the update/install flows and the customization record work in blocked issues #35 and #36, then trace how the agent/update path can access record metadata. Done means active records are loaded, per-customization outcomes are reported, configured validation or smoke checks run with failures surfaced, and success and incompatible cases are tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100