docs: establish integrated project memory
This commit is contained in:
21
.project-docs/90-maintenance/stale-items.md
Normal file
21
.project-docs/90-maintenance/stale-items.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# Stale Items
|
||||
|
||||
This is the integrated registry of stale or conflicting canonical memory. Update it only in Integration Gate.
|
||||
|
||||
## Possibly Stale Or Conflicting
|
||||
|
||||
| Date | Document | Issue | Source Task | Needed Confirmation |
|
||||
|---|---|---|---|---|
|
||||
|
||||
| 2026-08-12 | `server/internal/domain/experienced_people.go` | Comment says actual issued-ticket count, but callers supply cumulative issued party size and tests/SQL confirm people semantics | `20260812-finalize-native-display-7c23e18a` | Update the stale source comment in a future code task |
|
||||
|
||||
## Missing Context
|
||||
|
||||
- Original generator, speaker, and separate redistribution license for the historical Mandarin WAV fragments.
|
||||
- Target television density/font scale and final field acceptance evidence for APK 1.5.2.
|
||||
- Production Android signing owner and certificate/upgrade policy.
|
||||
- Product decision and route contract for the implemented-but-unregistered ticket transition/reissue handlers.
|
||||
|
||||
## Feature Task Routing
|
||||
|
||||
A feature task records new uncertainty in its own task record. When a separate conflict record is needed, write `90-maintenance/conflicts/{task_id}__<slug>.md`; do not append concurrent feature work here.
|
||||
Reference in New Issue
Block a user