views: find_by_tag endpoint + facade CDN 1.0.30 + host_config_layout + wc-content-kit

[AndrewKirkovski]

Summary

One big update consolidating four threads that ship together as the framework-side counterpart to gen-2-chat 1.0.30:

1. views: find_by_tag API — tag-name-keyed lookup for registered view.component entries (companion to gen-2-chat's $W.loadByTagName(tag)).
2. Facade CDN bump → 1.0.30 — across _index.yaml, README.md, Makefile, and the test fixture.
3. facade.host_config_layout ns.requirement — JSON-string config bag for managed-layout shells.
4. wc-content-kit module (NEW) — vendored mermaid / markdown / chartjs web components shipped from the framework so apps don't have to bundle them.

1. views: find_by_tag — tag-name → view.component lookup

Closes a gap in the FE isolation paradigm: there was no way to load a peer WC by its custom-element tag — loadWebComponent(componentId) only works on artifact UUIDs, and the only sanctioned path for static dependencies was auto_register: true + announced: true + customElements.whenDefined(). This adds the missing primitive.

Endpoint shape:

GET /components/by-tag/wc-thread-picker
→ 200 OK
{
  "success": true,
  "component": {
    "id": "...",
    "name": "...",
    "title": "...",
    "tag_name": "wc-thread-picker",
    "base_url": "http://localhost:8088/components/thread-picker/",
    "entry_point": "dist/index.js",
    "auto_register": true,
    "props": {...},
    "events": {...}
  }
}

GET /components/by-tag/no-such-tag
→ 404
{ "success": false, "error": "No view.component registered for tag: no-such-tag" }

Files (Lua):

• src/views/component_registry.lua — new find_by_tag_name(tag) library function. Returns the first matching view.component info or nil + error. Filters via registry.find({ "meta.type": "view.component", "meta.tag_name": tag }).
• src/views/api/find_by_tag.lua — new HTTP handler. 400 on missing tag, 404 on no match or unannounced, 403 on access denied. Respects the same announced + can_access checks as /components/list.
• src/views/api/_index.yaml — registers the function.lua + http.endpoint entries.
• src/views/_index.yaml — adds find_by_tag + find_by_tag.endpoint to the api_router targets.
• src/views/component_registry_test.lua — adds tag_name="test-widget" to the widget fixture + 3 new test cases (known tag, unknown tag, empty/nil tag).

Companion FE work (gen-2-chat 1.0.30, already published): $W.loadByTagName(tag, options?) proxy SDK function calls this endpoint then dynamic-imports + registers via the existing importESMComponentByPackageJSON pipeline. Per-tag in-flight dedup across all three FE load paths (loadByTagName, parseDomForLoaders, loadGlobalAutoloadWidgets), 30s whenDefined timeout, tag normalization at the boundary.

2. Facade CDN → 1.0.30

_index.yaml         fe_facade_url default   →  webcomponents-1.0.30
README.md           3 doc references         →  webcomponents-1.0.30
Makefile            WEB_HOST_CDN             →  webcomponents-1.0.30
config_handler_test  origin-extraction fixture →  webcomponents-1.0.30

The pre-existing branch state had _index.yaml and README.md stuck at 1.0.27 because the earlier merge that built this branch dropped the 1.0.28/1.0.29 bumps during conflict resolution. The final bump commit (bb97229) unifies all five locations on 1.0.30.

gen-2-chat 1.0.30 is published to npm (@wippy-fe/* 0.0.30, all 13 packages); CDN deploy to web-host.wippy.ai/webcomponents-1.0.30/ still pending.

3. host_config_layout ns.requirement

Added in feat(facade): add host_config_layout ns.requirement for managed-layout (commit on the feat/host-config-layout-requirement branch, merged in). Lets a managed-layout consumer ship its panel/floating/modal declaration as a JSON-string requirement value instead of hard-coding it in the consumer JS. Defaults to {}.

4. wc-content-kit module (NEW)

New top-level src/wc-content-kit/ shipping three production web components built from frontend/{mermaid,markdown,chartjs}/ Vite projects, served as static assets via http.static + http.endpoint. Apps consume via the same view.component registry as any other peer WC. Pre-built public/ artifacts checked in to keep the deploy story simple (no FE build step required in the framework's CI).

Lint

wippy lint --level error clean for both:

• src/facade (8 entries) — one lint error fixed in this PR (json.decode(entry.data.default) cast to string)
• src/views (pre-existing, clean)

Commits

Hash	Subject
feat(wc-content-kit)	new module shipping mermaid / markdown / chartjs
feat(facade)	host_config_layout ns.requirement for managed-layout
1fa60c3	Bump facade CDN to 1.0.28
55e55b5	Bump facade CDN to 1.0.29
310ea47	facade: drop live-yaml-test marker
merge	origin/feat/host-config-layout-requirement into chore/bump-facade-cdn-1.0.28
merge fix	restore extra_scripts content lost during conflict resolution
views	add find_by_tag_name lookup + GET /components/by-tag/{tag}
bb97229	Bump facade CDN to 1.0.30 + fix lint error

Cross-repo coordination

• gen-2-chat 1.0.30 — published to npm (all 13 @wippy-fe/* at 0.0.30), deploy to web-host.wippy.ai/webcomponents-1.0.30/ pending.
• PR Bump facade CDN to 1.0.29 #55 — superseded by this PR (the 1.0.29 facade bump is included here via the base merge, then bumped to 1.0.30 on top). Safe to close after views: find_by_tag endpoint + facade CDN 1.0.30 + host_config_layout + wc-content-kit #56 lands.