TASK22211: version memory-bank and backfill change-log stream
This commit is contained in:
@@ -0,0 +1,57 @@
|
||||
# Open Questions
|
||||
|
||||
## Entry Template
|
||||
|
||||
```
|
||||
date: YYYY-MM-DD
|
||||
author: <agent|name>
|
||||
scope: <files/routes/features>
|
||||
type: question
|
||||
rationale: <why unresolved>
|
||||
impact: <user/system/security/i18n/a11y>
|
||||
status: open|resolved
|
||||
|
||||
Question:
|
||||
Needed from:
|
||||
Decision deadline:
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Q-001: Auth Logging Redaction Standard
|
||||
|
||||
date: 2026-03-11
|
||||
author: Cline
|
||||
scope: auth/email APIs and actions logging
|
||||
type: question
|
||||
rationale: Existing logging appears verbose in sensitive flows.
|
||||
impact: Potential privacy/security exposure via operational logs.
|
||||
status: open
|
||||
|
||||
Question:
|
||||
What mandatory redaction and logging policy should be enforced for auth/email/document flows?
|
||||
|
||||
Needed from:
|
||||
Security lead + application owner
|
||||
|
||||
Decision deadline:
|
||||
Before next auth/notification release
|
||||
|
||||
### Q-002: Test Strategy Baseline for Sparse `tests/`
|
||||
|
||||
date: 2026-03-11
|
||||
author: Cline
|
||||
scope: testing strategy repository-wide
|
||||
type: question
|
||||
rationale: `tests/` currently appears minimal; validation relies heavily on manual checks.
|
||||
impact: Increased regression risk and slower release confidence.
|
||||
status: open
|
||||
|
||||
Question:
|
||||
What minimum automated coverage should be required per change type (feature, bug fix, high-risk integration)?
|
||||
|
||||
Needed from:
|
||||
Engineering lead + QA
|
||||
|
||||
Decision deadline:
|
||||
Before next major feature cycle
|
||||
Reference in New Issue
Block a user