Talon/chat_grid
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(plan): add explicit 1-6 completion status

Browse Source
This commit is contained in:
Jage9
2026-02-24 19:01:33 -05:00
parent 3c52d35983
commit 59db0a0dda
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
plans/item-architecture-refactor-plan.md
View File

@@ -320,3 +320,12 @@ When adding a new item type:
### Recommendations / Cleanup (remaining) ### Recommendations / Cleanup (remaining)
1. **Eliminate manual property label mapping in client (medium):** either include labels for all properties in server metadata or auto-humanize keys so new properties are readable without code changes. 1. **Eliminate manual property label mapping in client (medium):** either include labels for all properties in server metadata or auto-humanize keys so new properties are readable without code changes.
2. **Strengthen new-item completeness checks (low):** extend the plugin contract tests to optionally assert docs coverage and richer protocol examples per discovered type. 2. **Strengthen new-item completeness checks (low):** extend the plugin contract tests to optionally assert docs coverage and richer protocol examples per discovered type.
### Item 1-6 Status (explicit)
1. **visibleWhen end-to-end:** ✅ Done.
2. **Remove hardcoded item-type literals/enums:** ✅ Done (string-based ids + runtime known-type checks).
3. **Include capabilities in `uiDefinitions.itemTypes`:** ✅ Done.
4. **Move list options into property metadata:** ✅ Done (`propertyMetadata[key].options` only).
5. **Remove manual client property-label mapping:** ❌ Not fully done yet. Metadata labels are supported, but legacy hardcoded label map still exists as fallback.
6. **New-item completeness validation check:** ✅ Baseline done (plugin contract tests added for required files/exports).
Potential enhancement: add docs/protocol example assertions for each discovered type.