Idea: component packs V1+ extensions

[merlin-the-ai]

Summary

Follow-up to #64 for component-pack changes that should come after the V1 issue chain.

V1 is intentionally narrow: trusted local/project/user pack manifests, structural safety validation, deterministic JS/CSS asset handling, sanitized-mode allowlists, visible pack metadata, and hard failures for duplicate or reserved tag ownership.

V1 implementation issues:

• Component Packs V1: trusted local/user/project packs #68 — Component Packs V1: trusted local/user/project packs
• Component Packs 1/6: add V1 pack manifest model and loader #69 — Component Packs 1/6: add V1 pack manifest model and loader
• Component Packs 2/6: resolve explicit, project, and user pack inputs #70 — Component Packs 2/6: resolve explicit, project, and user pack inputs
• Component Packs 3/6: enforce tag ownership and conflict policy #71 — Component Packs 3/6: enforce tag ownership and conflict policy
• Component Packs 4/6: extend sanitized mode from pack manifests #72 — Component Packs 4/6: extend sanitized mode from pack manifests
• Component Packs 5/6: copy pack assets and inject deterministic metadata #73 — Component Packs 5/6: copy pack assets and inject deterministic metadata
• Component Packs 6/6: add V1 diagnostics, docs, and demo fixture #74 — Component Packs 6/6: add V1 diagnostics, docs, and demo fixture

V1+ modifications to explore

• npm package packs: resolve installed packages and support agentIsles.pack in package.json or root agent-isles.pack.json.
• git repo packs: pinned refs/tags/commits, cache layout, clear warnings for unpinned refs, and no automatic npm install / build-script execution during render.
• Strict manifest validation: required attributes, enum/range checks, slot constraints, accessibility hints, and a future strict mode or isles packs validate <pack> workflow.
• Pack authoring tools: templates, schema publishing, example packs, and documentation for safe custom-element prefixes.
• Advanced asset concerns: dependency/version dedupe, integrity metadata, shared assets, and compatibility diagnostics.
• Community/distribution patterns once V1 proves the local manifest model.

Locked boundaries from the V1 discussion

• User-scoped packs should load automatically from user config, with --no-user-packs for reproducibility.
• Unpinned git refs should warn rather than fail when git sources are added.
• No override mode for core <agent-*> tags or third-party tag conflicts.
• Do not turn packs into arbitrary renderer plugins; V1+ should still prefer declared manifests and prebuilt browser assets.