From 59db0a0dda4d9cf4d92df9480b06c1320ed93510 Mon Sep 17 00:00:00 2001 From: Jage9 Date: Tue, 24 Feb 2026 19:01:33 -0500 Subject: [PATCH] docs(plan): add explicit 1-6 completion status --- plans/item-architecture-refactor-plan.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/plans/item-architecture-refactor-plan.md b/plans/item-architecture-refactor-plan.md index 261faf6..27bc1bd 100644 --- a/plans/item-architecture-refactor-plan.md +++ b/plans/item-architecture-refactor-plan.md @@ -320,3 +320,12 @@ When adding a new item type: ### 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. 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.