Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.
TypeScript browser-shellcontrol-planefile-managerhomelabmobile-firstnextjsptyreactself-hostedserver-managementshadcn-uisysadmintailwindcssterminaltypescriptvpsweb-desktopweb-terminal
chore(release): reconcile workflow tabs with verified security closeout
Rahmand6547550f04f
diff --cc docs/CHANGELOG.mdindex 77b368a4,ae4c7013..a5ba423f--- a/docs/CHANGELOG.md+++ b/docs/CHANGELOG.md@@@ -13,7 -12,8 +13,9 @@@ this is the *what*, and it is what Sett**Fixed**+- `workflows` keep runtime registry out of deployment tracing+ - `security` apply existing ZAP informational policy explicitly+ - `security` require executed passive scan evidence- `browser` retain private viewer connectivity without server access- `release` align Node support and read-only browser reconnects- `extensions` lock project controls until initial inspectiondiff --cc docs/PROGRESS.mdindex e41fc9c6,9cc67c35..b0b4b1c5--- a/docs/PROGRESS.md+++ b/docs/PROGRESS.md@@@ -1,11 -1,18 +1,26 @@@+## 2026-09-18 — Reviewed workflow provider tabs++- Keep the native automation/session editor unchanged and mounted while switching to external workflow editors such as n8n. The new wrapper consumes explicit workflow placements in the existing owner-reviewed surface registry, not app-store HTML or credential values.+- Share the registry outside the MCP transport without adding another store. Owner-only no-store metadata and revision-checked, explicitly reviewed configuration APIs/CLI preserve exact origins, unrelated entries, safe sandbox permissions and remote-only fallback. Configuration input cannot carry paths or credentials.+- Workflow-only placements never grant an MCP Page nested-frame origin. Load frames only on demand, preserve editor state when switching, expose top-level sign-in/open/reload actions and keyboard-accessible tabs. Browser login remains external-service-owned; framing never means MCP token forwarding or authentication bypass.+- Add registry/access tests and a mandatory isolated browser journey with synthetic stores. Live n8n frame checks wait for actual nonblank paint as well as visible controls; keep the synthetic approved parent and signed-out proof distinct from authenticated editor claims.+- The strict release build caught project-wide tracing of the dynamic registry path. Mark that owner-local runtime read as a non-build input, matching other private stores; the warning-fatal release gate remains unchanged.++ ## 2026-09-18 — Require executed passive security scan evidence++ The security closeout found that the scheduled hosted ZAP workflow could report+ success while its only scan step was skipped when no target was configured. Add a+ dependency-free target guard before an unconditional passive scan. Missing, unsafe+ or credential-bearing targets fail without echoing their contents; existing scanner+ pins, passive scope, rule classifications and alert failures remain unchanged.+ Tests exercise the CLI refusal and workflow wiring. Security assurance guidance now+ separates successful code/dependency/secret checks from historical alert dismissals+ and passive-scan execution; no dismissal or badge attestation is performed.+ The first executed hosted scan exposed a second wiring error: the pinned ZAP action+ only forwarded its policy input when it found IGNORE entries. Pass the existing+ INFO-only file explicitly with `-c`; preserve all five informational findings, new+ warning failures and the original policy bytes rather than inventing new exceptions.+## 2026-09-18 — Keep private viewer routing client-verifiableThe PR review reproduced a deployment-compatibility regression: a hostname resolving