web: give stim a display pane #15

Merged

perishadmin merged 4 commits from stim-cold-start into main

2026-07-29 06:30:57 +00:00

perishadmin commented

2026-07-29 06:23:25 +00:00

Contributor

web: give stim a display pane

stim had one workload and no interaction surface. It now carries an
apps/web pane on the workshop's design system, and a second sidecar
workload to run it.

The pane is deliberately thin: a view holds no fetch of its own, and
reaches the api only through src/lib/hooks. That directory is already a
first-class one under the skeleton's web law, so the hooks layer needed
no new convention invented for it.

Two things the checkers taught rather than confirmed. Bringing apps into
ectropy's scan immediately refused a hand-written vite proxy that read
API_URL, because plumb already forbids an app consuming sidecar dispatch
environment by hand -- vite-plugin-design owns that proxy and follows the
api lease itself. And the same pass demanded the boundary declarations
for vite's root-level config files, which is the law asking to be told
rather than guessing.

The layering this is built toward, and why the CLI is a display pane
rather than a privileged entrance, is now written into AGENTS.md as
prose. It stays prose until the shape is settled enough to mechanize.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

web: give stim a display pane stim had one workload and no interaction surface. It now carries an apps/web pane on the workshop's design system, and a second sidecar workload to run it. The pane is deliberately thin: a view holds no fetch of its own, and reaches the api only through src/lib/hooks. That directory is already a first-class one under the skeleton's web law, so the hooks layer needed no new convention invented for it. Two things the checkers taught rather than confirmed. Bringing apps into ectropy's scan immediately refused a hand-written vite proxy that read API_URL, because plumb already forbids an app consuming sidecar dispatch environment by hand -- vite-plugin-design owns that proxy and follows the api lease itself. And the same pass demanded the boundary declarations for vite's root-level config files, which is the law asking to be told rather than guessing. The layering this is built toward, and why the CLI is a display pane rather than a privileged entrance, is now written into AGENTS.md as prose. It stays prose until the shape is settled enough to mechanize. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

perishadmin added 1 commit

2026-07-29 06:23:25 +00:00

web: give stim a display pane

guard / guard (pull_request) Failing after 12s

Details

876118f7d8

stim had one workload and no interaction surface. It now carries an
apps/web pane on the workshop's design system, and a second sidecar
workload to run it.

The pane is deliberately thin: a view holds no fetch of its own, and
reaches the api only through src/lib/hooks. That directory is already a
first-class one under the skeleton's web law, so the hooks layer needed
no new convention invented for it.

Two things the checkers taught rather than confirmed. Bringing apps into
ectropy's scan immediately refused a hand-written vite proxy that read
API_URL, because plumb already forbids an app consuming sidecar dispatch
environment by hand -- vite-plugin-design owns that proxy and follows the
api lease itself. And the same pass demanded the boundary declarations
for vite's root-level config files, which is the law asking to be told
rather than guessing.

The layering this is built toward, and why the CLI is a display pane
rather than a privileged entrance, is now written into AGENTS.md as
prose. It stays prose until the shape is settled enough to mechanize.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

PerishFire added 1 commit

2026-07-29 06:24:17 +00:00

guard: install the workspace before the gauntlet

guard / guard (pull_request) Failing after 46s

Details

ad90281887

The lane gained a web app but not the step that makes one buildable, so
CI ran biome, tsc, vitest, and the vite build against a tree with no
node_modules while the local guard passed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

PerishFire added 1 commit

2026-07-29 06:25:34 +00:00

guard: let the lane run pnpm

guard / guard (pull_request) Failing after 40s

Details

95f225b97a

The workspace install landed but the deno permission list in the lane
did not, so CI still refused to spawn pnpm. The runseal profile and the
lane carry that list separately; both had to learn the same name.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

PerishFire added 1 commit

2026-07-29 06:28:22 +00:00

guard: name the collision between two laws

guard / guard (pull_request) Successful in 2m22s

Details

ad936d5f23

CI installs ectropy v0.4.0-beta.1, which stopped reporting word findings
as debt and started failing on them. The offending identifier is the
file name itself: use-health.

That is not a defect in this repository. plumb's web law *requires*
hooks to be named use-*.ts, and ectropy's word law requires an
identifier to be one word. The two-word spelling is mandated by the
first law and refused by the second, so any repository that grows a
hooks directory under the skeleton's web shape will hit it.

Declared as a boundary here rather than renamed, because renaming would
break the law that is checked by the doctor to satisfy the law that is
checked by the checker. Filed upward separately.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

perishadmin merged commit be8e7cdf7e into main

2026-07-29 06:30:57 +00:00

perishadmin deleted branch stim-cold-start

2026-07-29 06:30:57 +00:00

perishadmin referenced this pull request from a commit

2026-07-29 06:30:59 +00:00

web: give stim a display pane (#15)