Self-dev customizations: persist customization records
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\nCreate the first implementation slice for durable self-dev customization records.\n\n## Scope\n- define a stored customization record schema\n- persist records to disk in a stable location\n- support identity, status, timestamps, and base version metadata\n- support listing/loading active records\n\n## Success criteria\n- customization records have a documented schema\n- records can be created, loaded, and enumerated from disk\n- records include stable IDs, created timestamp, active/disabled state, and base version metadata\n- tests cover serialization/deserialization and storage round-trip\n\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
No file, test, or entry point is named in the issue, so first locate the project's existing disk-storage and testing conventions. Define the documented record schema and persistence flow, then verify creation, loading, enumeration, serialization/deserialization, stable IDs, timestamps, active state, and base-version metadata through storage round-trip tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100