docs(15): create phase plan
This commit is contained in:
@@ -844,20 +844,20 @@ DATA_c6d9k2hx_END
|
||||
|
||||
**If this table is empty:** not applicable — four assumptions remain.
|
||||
|
||||
## Open Questions
|
||||
## Open Questions (RESOLVED)
|
||||
|
||||
1. **Should plan 01 still include "add cabana markdown"?**
|
||||
- What we know: 14.2.1 already shipped the types and SPA controls.
|
||||
- What's unclear: whether the planner treats D-11 as a checkbox that needs a tagged no-op.
|
||||
- Recommendation: no-op D-11; Journal uses `mlmarkdown`. Mention in plan 02 YAML only.
|
||||
- RESOLVED: no-op D-11; Journal uses `mlmarkdown`. Mention in plan 02 YAML only.
|
||||
|
||||
2. **On-the-fly tags (`customTags: true`)**
|
||||
- What we know: cabana has no taglist type.
|
||||
- Recommendation: relation picker + Tags admin. Do not add a framework type this phase.
|
||||
- RESOLVED: relation picker + Tags admin. Do not add a framework type this phase.
|
||||
|
||||
3. **Optional backend principal helper**
|
||||
- What we know: cabana guard is all-or-nothing middleware.
|
||||
- Recommendation: small function in the journal plugin that Lookup's `bouncer.Registry` guard `"backend"` if the header is present.
|
||||
- RESOLVED: small function in the journal plugin that Lookup's `bouncer.Registry` guard `"backend"` if the header is present.
|
||||
|
||||
These are execution details inside Claude's Discretion, not blockers.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user