future-plans: type field approach for item types, bulk migration strategy

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

future-plans.md

@@ -356,8 +356,13 @@ multiple item types (components, bins, tools, materials, etc.) with:
 - The current components section becomes one such type-specific view rather than
   the only view
 
-This is a significant architectural change — not needed now, but should inform data
-model decisions so we don't paint ourselves into a corner.
+**Implementation approach:** Add a `type` field to items (e.g. `component`, `bin`,
+`tool`). Type-specific views are just filtered views over all items. No separate
+collection or schema per type — the type field drives which view renders it.
+
+**Migration:** Bulk assignment via the existing field system — e.g. set `type =
+"component"` on all current items in one operation, since they're all components.
+No per-item manual work needed.
 
 ### Inventory URL reflects selected entry
 Similar to how components now reflect `/components/:id` in the URL, inventory