Tests fixes, audit progress, UI completions
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
# BinaryIndex Persistence Tests Charter
|
||||
|
||||
## Mission
|
||||
Validate BinaryIndex persistence behavior with deterministic integration tests.
|
||||
|
||||
## Responsibilities
|
||||
- Maintain `StellaOps.BinaryIndex.Persistence.Tests`.
|
||||
- Keep tests deterministic and offline-friendly with controlled fixtures.
|
||||
- Surface open work on `TASKS.md`; update statuses (TODO/DOING/DONE/BLOCKED/REVIEW).
|
||||
|
||||
## Key Paths
|
||||
- `BinaryIndexIntegrationFixture.cs`
|
||||
- `BinaryIdentityRepositoryTests.cs`
|
||||
- `CorpusSnapshotRepositoryTests.cs`
|
||||
|
||||
## Coordination
|
||||
- Persistence and Infrastructure.Postgres teams.
|
||||
|
||||
## Required Reading
|
||||
- `docs/modules/binaryindex/architecture.md`
|
||||
- `docs/modules/platform/architecture-overview.md`
|
||||
|
||||
## Working Agreement
|
||||
- 1. Update task status to `DOING`/`DONE` in both corresponding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
|
||||
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
|
||||
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
|
||||
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
|
||||
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
|
||||
Reference in New Issue
Block a user