Stencil setup

Application pending. Commands below are grounded in inspected upstream sources, not deployment evidence. Return to index.

flowchart LR
  A[Pinned source] --> B[Install and adapt]
  B --> C[Static output]
  C --> D[Browser and access proof]

Source choice

The Stencil 4.45.1 release is the verified stable core release, published 2026-09-23. create-stencil 4.0.2 is the verified generator. Before starting this application, the release owner must reread the user’s latest Stencil community-source direction; no additional exact community URL was available during initial research.

The community app starter last changed on 2024-11-09 and pins core 4.22.2. Its existence does not establish current maintenance. The archived ionic-pwa-toolkit is explicitly excluded.

Prepare current dependencies

These source-derived commands have not run. From the project apps directory with an unused destination:

nice -n 10 npm init stencil@4.0.2 app stnl
cd stnl
nice -n 10 npm install --save-dev --save-exact @stencil/core@4.45.1

Inspect generated dependencies and lock them; do not assume the generator selected current packages. Use only packages exercised by the workbench. Verified candidates are:

Package	Verified version	Role
@ionic/core	9.0.5	Maintained Stencil-built visual components
@stencil-community/context	1.0.0	Community context utility, not a visual library
@stencil-community/unplugin-stencil	0.5.2	Compiler integration utility, not a visual library
@stencil/store	2.2.4	Shared state utility
@stencil/sass	3.3.3	Sass integration, only if needed

Stencil community and Ionic components provide the upstream context. Namespaced packages are not automatically maintained: the router’s observed 2024 update is not a current-maintenance claim.

Output and component contract

The upstream app config uses a www output target with serviceWorker: null. The showcase’s intended output is apps/stnl/www:

nice -n 10 npm run build

A separately configured dist-custom-elements output target is needed for the shared custom element; the www output alone does not provide that integration. The planned <omp-chat-bubble site="fuma|hkit|stnl"> interface is a deployment contract, not an implemented component at this phase. The workbench should demonstrate functional controls, state transitions, keyboard interaction, and responsive layout with real maintained components.

Acceptance still required

Prove the workbench beyond its initial starter screen, including keyboard behavior and narrow/wide layouts. Verify custom-element loading independently on all three site stacks with no console errors. The application and component assets must share their application’s authentication boundary. Shared chat must exercise real OMP inference, citations, a useful unavailable/error state, and a source-bounded refusal; the static component build alone proves none of those backend behaviors.