bedrock-flows 0.7.1

package/template/.storybook/preview-head.html

@@ -0,0 +1,35 @@
+<!--
+  The compiled design-system bundle (global.css + every component.css), served
+  by Storybook's staticDirs mapping (../design-system/<version> -> /ds-current).
+  Without this link every story renders unstyled. Relative href so it resolves
+  under the production base (/ds/<version>/storybook/) and in dev alike.
+-->
+<link rel="stylesheet" href="ds-current/style.css" />
+
+<!--
+  Injected into every story iframe.
+
+  The comment panel + sidebar count badges live in manager-head.html (top
+  window). The only behaviour needed inside the preview iframe is keeping
+  Figma links from hijacking the docs frame: a Figma anchor without a target
+  would replace the story iframe on click, so rewrite them to open a new tab.
+  (The source repo also injected Ziptility-specific docs chrome + DS behaviour
+  scripts here — those are design-system content, not the commenting feature,
+  so they are intentionally not ported.)
+-->
+<script>
+  (function () {
+    function blankFigmaLinks(root) {
+      const links = (root || document).querySelectorAll('a[href*="figma.com"]:not([data-blank])')
+      links.forEach(function (a) {
+        a.setAttribute('target', '_blank')
+        a.setAttribute('rel', 'noopener')
+        a.setAttribute('data-blank', '1')
+      })
+    }
+    blankFigmaLinks(document)
+    new MutationObserver(function () {
+      blankFigmaLinks(document)
+    }).observe(document.documentElement, { childList: true, subtree: true })
+  })()
+</script>

package/template/.storybook/preview.js

@@ -0,0 +1,23 @@
+/**
+ * Per-story configuration applied across the storybook.
+ *
+ * Required for Storybook 10's autodocs path: without a preview.js sibling to
+ * main.js, the html-vite framework renderer isn't attached to the docs
+ * preparedMeta, and every Docs page throws `r.renderer is not a function`.
+ */
+
+/** @type {import('@storybook/html-vite').Preview} */
+const preview = {
+  parameters: {
+    layout: 'centered',
+    options: {
+      // Sidebar bucket order: Foundations (tokens) → Components (interactive
+      // UI) → Utilities (layout primitives). Reads top-down from "what does it
+      // look like" to "how do I assemble it".
+      storySort: { order: ['Foundations', 'Components', 'Utilities'] },
+    },
+  },
+  tags: ['autodocs'],
+}
+
+export default preview

package/template/CHANGELOG.md

@@ -0,0 +1,236 @@
+# Changelog
+
+All notable changes to Bedrock Flows are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+Versions 0.1.0 and 0.2.0 were tagged retroactively when this changelog was
+introduced (alongside 0.3.0); from 0.3.0 on, tag at release time and keep an
+`Unreleased` section at the top between releases.
+
+## [Unreleased]
+
+## [0.7.1] — 2026-06-13
+
+### Fixed
+
+- **Unpinned the better-auth stack — the defensive `pnpm.overrides` lock is
+  lifted.** `better-auth` + `@better-auth/kysely-adapter` + `@better-auth/infra`
+  move to `1.6.18` / `1.6.18` / `0.2.14`, and `kysely` floats up to `0.29.2`
+  (from `0.28.17`). The pin existed because the old adapter imported
+  `DEFAULT_MIGRATION_LOCK_TABLE` from kysely, which kysely removed in `0.29.0` —
+  breaking the worker bundle. better-auth has since inlined that constant, so
+  the import no longer depends on kysely exporting it and the pin is obsolete.
+  Verified end-to-end: worker bundle builds, and a live sign-up writes to D1
+  through the kysely-d1 adapter on kysely `0.29.2`. (One non-fatal cosmetic
+  peer-dependency warning remains until `@better-auth/sso` ships `1.6.18`.)
+
+## [0.7.0] — 2026-06-13
+
+Surfaced by real use in the Ziptility child project: the wireflow now respects
+each flow's intended viewport range, sign-in UI ships from the package, and the
+agentic comment loop's "needs a human" decision is visible.
+
+### Added
+
+- **The `auth` package now ships the sign-in UI, not just the auth backend.**
+  New exports `renderSigninPage()` / `signinPageResponse()` return a
+  self-contained, server-rendered `/signin` page (the canonical `.bf-auth-*`
+  markup + inlined `auth-gate.css` styling + plain-fetch JS against
+  `/api/auth/*`), and `handleAuthRequest` now serves `GET /signin` and
+  `/signin.html` directly. Previously the package exposed only the backend
+  (`createAuth`, `handleAuthRequest` for `/api/auth/*` + `/__wf-people`,
+  `getSessionUser`), so every consuming project had to hand-maintain its own
+  sign-in page — the child `ziptility-feature-pipeline-prototypes` carried a
+  stale `public/signin.html` fork that had drifted from the canonical gate
+  (no field labels, a Google button that hugged its content instead of
+  filling the card). A project's worker can now delete its local sign-in page
+  and serve the package's instead, optionally customising title/lede/Google
+  via `handleAuthRequest(req, env, { signin: { … } })`.
+
+- **The wireflow canvas now honors the intended viewport range.** The
+  per-flow range (`meta.json` `viewport` over the DS version's `ds.json`
+  `intendedViewport`, resolved via `bedrock.resolveViewport`) is injected into
+  the wireflow and consumed by the canvas Viewport control exactly as the
+  detail-screen control already did: out-of-range breakpoints are marked
+  (advisory, still clickable), an "Intended: min–max" footer shows the range +
+  its source, the default lands inside the range, and the chosen breakpoint is
+  now stored **per-flow** (`protoNavViewport:<id>`) so a desktop pick no longer
+  bleeds onto a mobile flow. Closes the gap where a mobile flow rendered
+  desktop-shaped node iframes.
+
+- **Wireflow max-zoom is derived from the viewport range.** Instead of a fixed
+  800% cap for every flow, the canvas zoom-in ceiling scales with the largest
+  allowed width: a mobile range (~440px) tops out ~4× (≈400%), a laptop range
+  (~1440px) earns the full 8× (≈800%). A screen is shrunk into its node, so the
+  useful max zoom is roughly what shows the largest allowed screen at
+  ~life-size + a little headroom — larger allowed widths earn more zoom.
+
+- **`needs-human` comment badge.** When the agentic loop considers a comment
+  but defers to a human (sets `status: needs-human`), the comment now shows a
+  soft-blue "Needs human" pill — same treatment as the green Resolved badge —
+  on both the wireflow and detail-screen comment panels, so a considered-
+  but-deferred comment is no longer indistinguishable from an untouched one.
+
+## [0.6.0] — 2026-06-12
+
+The npm release: the platform engine ships as a single published package,
+and a project's dependency version states the platform release it runs.
+
+### Changed
+
+- **The platform publishes as one npm package:
+  `@obra-studio/bedrock-flows`.** Its version number IS the platform release.
+  The workspace keeps its per-package structure for development (internal
+  scope renamed `@bedrock3/*` → `@bedrock-flows/*`, never published);
+  `node scripts/publish-umbrella.mjs` assembles the umbrella at publish time —
+  every package becomes a subpath export (`/core`, `/config`, `/auth`,
+  `/wireflow/client`, `/design-system/manifest`, …, with the root re-exporting
+  config so `import { defineConfig } from '@obra-studio/bedrock-flows'`
+  works), internal imports become self-referencing subpaths, and runtime
+  dependencies merge (exact `better-auth@1.6.9` pins carry through — root
+  pnpm overrides don't reach npm consumers). Licensed **FSL-1.1-MIT**
+  (Functional Source License: free for any non-competing use, each release
+  becomes MIT after two years; commercial licensing: johan@obra.studio).
+  This is phase 1 of platform-as-dependency: children will delete
+  `packages/*` and depend on the umbrella, shrinking the sync surface to
+  the chrome, harness assets, and apps.
+
+## [0.5.1] — 2026-06-12
+
+The portability release: child deployments can now upgrade with one command,
+and per-project values move out of platform files so that upgrade is lossless.
+
+### Added
+
+- **`sync-child` upgrade script.** `node scripts/sync-child.mjs <child> --check`
+  detects which platform release a same-shaped child effectively runs and
+  lists its local drift; `--apply --tag vX.Y.Z --branch` upgrades the child's
+  platform files wholesale on an `upgrade/<tag>` branch, stamps the version,
+  and runs install + build. Child-owned files (worker config, chrome plugin
+  toggles/breakpoints) are never touched.
+- **Dashboard dev sign-in on :5173.** Upstreamed from the UGent child: the
+  dashboard dev server pins port 5173 and proxies auth/comments/people/spec
+  routes to the wrangler worker on :8787, so local sign-in works without
+  switching origins.
+
+### Changed
+
+- **Per-project values leave platform files.** The dashboard's comments
+  origin now comes from the project's `bedrock.config.ts`
+  (`modules.commenting.prodOrigin`, injected at build time) instead of a
+  hardcoded URL — every deployment must point at its **own** worker, never
+  another project's. Storybook's fallback DS version likewise follows the
+  project's `defaultDsVersion`.
+
+## [0.5.0] — 2026-06-12
+
+The cleanup release: two deprecated subsystems leave the platform.
+
+### Removed
+
+- **Template sets.** The deprecated template-sets module is gone — the
+  `@bedrock3/template-sets` package, the `/t` routes, the shared
+  `template-set.njk` chrome, and every `templateSet` / `isTemplateSet` branch
+  across config, core, the wireflow, the worker, and the dashboard. No
+  content was affected; no prototype declared a template set.
+- **Spec-view inline comments.** The spec view's inline-comment layer
+  (selection → comment button, thread popover, quote-match highlights) is
+  removed, superseded by the spec-composer margin-comment direction. Spec
+  display and in-place editing keep working unchanged.
+
+## [0.4.2] — 2026-06-12
+
+The viewport-intent release: design systems and flows declare the resolution
+range they're designed for, and the review chrome keeps everyone honest
+about it. (Supersedes the 0.4.0/0.4.1 iterations of the same feature.)
+
+### Added
+
+- **Intended viewport range.** A design system can now declare the resolution
+  range it's designed for (`design-system/<version>/ds.json` →
+  `intendedViewport`), and any flow can override it in its `meta.json`
+  (`viewport`) — so a phone-only flow can span small phone to large phone
+  while a responsive web flow spans small phone to laptop. Ranges are written
+  as raw `{ "w": …, "h": … }` CSS pixels (the canonical format) or as generic
+  device-class shorthand carrying the looked-up logical resolution of a
+  reference device: `small-phone` 375×812 (iPhone 12 mini), `phone` 402×874
+  (iPhone 16 Pro / 17), `large-phone` 440×956 (iPhone 17 Pro Max),
+  `square-foldable-phone` 984×1092 (Galaxy Z Fold 7 unfolded), a tablet
+  family in portrait + wide variants — `small-tablet` 744×1133 (iPad mini),
+  `tablet` 834×1210 (iPad Pro 11"), `large-tablet` 1032×1376 (iPad Pro 13") —
+  plus `trifold` (= `tablet-wide`), `small-laptop` 1280×800, `laptop`
+  1440×900, `medium-desktop` 1920×1080, and `large-desktop` 2560×1440. The
+  screen chrome's Viewport control shows the intended range, dims breakpoints
+  outside it, and the drag-resize readout turns amber when you leave it —
+  advisory, never a clamp.
+- **In-app changelog + version badge.** The sidebar shows the release you're
+  running; clicking it opens this changelog as a page in the app (also
+  reachable via ⌘K).
+
+## [0.3.0] — 2026-06-12
+
+The roles & review-flow release: comments learn who said what and what agents
+may act on, and design content goes behind sign-in.
+
+### Added
+
+- **Manager role + designer approval flow.** A new manager role joins
+  user/designer/admin. Manager comments are never directly actionable: they
+  arrive as "pending review", and a designer approves them — optionally
+  adding context for the agent — before anything gets designed. Every
+  comment panel shows the pending state and gives designers an inline
+  approve-with-context composer.
+- **Role management in user admin.** Each user can be set to one of four
+  roles: user (reviewer) · manager (comments need designer approval) ·
+  designer (actionable comments, approves managers) · admin (designer plus
+  user management).
+- **Node-anchored comments (experimental).** Screen comments can anchor to a
+  specific element rather than the whole screen.
+- **Side-note opt-out + commented viewport.** A compose-time toggle marks a
+  comment as a side note (excluded from the agentic loop), and every comment
+  records the viewport it was made at; the queue preview renders that exact
+  viewport instead of full page height.
+- **Comment polish.** URLs linkified in comment text; resolved comments drop
+  the strikethrough; card layout reworked (chips on their own row, byline on
+  its own line).
+
+### Changed
+
+- **Design content now requires sign-in.** Flows, screens, and design-system
+  pages are gated the same way the dashboard is — nothing is reachable
+  anonymously anymore.
+
+## [0.2.0] — 2026-06 (retroactive)
+
+The harness & comments wave.
+
+### Added
+
+- **Responsive Viewport preview** for flow screens and the wireflow.
+- **Touch-device harness chrome**, plus a `d` shortcut to toggle chrome
+  light/dark.
+- **DS X-ray + ⌘K palette** (current iteration), including the clickthrough
+  from an x-rayed element to its Storybook story.
+- **Comment image attachments**, clipboard paste, a shared lightbox with the
+  comment text as caption, and images attached to queue reopen notes.
+
+### Changed
+
+- Wireflow zoom cap raised from 400% to 800%; wireflow node hit area pinned
+  to the frame width.
+- Sign-in screen polish: visible labels, consistent typography.
+
+## [0.1.0] — 2026 (retroactive)
+
+The platform foundation.
+
+### Added
+
+- **Bedrock Flows**: a dashboard of linkable feature flows (wireflows) with
+  per-screen commenting, versioned design-system storybooks, and the agent
+  designs queue.
+- **Accounts**: invite-only sign-up with email verification, Google sign-in,
+  and in-app user management with email invites.
+- **DS X-ray**: see which design-system pieces a screen is built from.
+- **Front-end deliveries**: a page-tree of delivered front-ends, landing on
+  the home page.

package/template/README.md

@@ -0,0 +1,26 @@
+# Bedrock Flows — project
+
+This project runs the **published** Bedrock Flows platform (`@obra-studio/bedrock-flows`). You edit
+the content; the platform comes from npm. Upgrade with `npm install @obra-studio/bedrock-flows@latest`.
+
+## What you edit
+- `prototypes/` — wireflow prototypes (one folder per flow; `_shared/` holds the page templates).
+- `design-system/` — versioned design systems (`<version>/components/<name>/{component.css,macro.njk,variants.json}`).
+- `bedrock.config.ts` — which modules are enabled + this project's comment `prodOrigin`.
+
+## Develop
+```bash
+npm install
+npm run dev       # one command: worker + dashboard + design-system storybook
+```
+Open <http://localhost:5173>. First run generates `apps/worker/.dev.vars`
+automatically — no setup needed.
+
+## Deploy
+```bash
+npm run deploy                            # builds, then wrangler deploy
+```
+Cloudflare resources (KV, D1, secrets) are set up separately.
+
+> Scaffolded by `npx bedrock-flows create`. The platform wiring here is generated —
+> change it upstream, not in this project.

package/template/apps/dashboard/index.html

@@ -0,0 +1,15 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Bedrock Flows</title>
+    <!-- Shared auth-gate card styling — single source across dashboard/wireflow/screen. -->
+    <link rel="stylesheet" href="/auth-gate.css" />
+  </head>
+  <body>
+    <div id="root"></div>
+    <script type="module" src="/src/main.tsx"></script>
+      <script src="/lightbox.js" defer></script>
+  </body>
+</html>

package/template/apps/dashboard/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "@bedrock-flows/dashboard",
+  "version": "0.0.0",
+  "private": true,
+  "type": "module",
+  "description": "Dashboard SPA — thin shell that assembles enabled modules into the sidebar",
+  "scripts": {
+    "dev": "vite",
+    "build": "vite build",
+    "preview": "vite preview"
+  },
+  "dependencies": {
+    "@obra-studio/bedrock-flows": "__BEDROCK_FLOWS_VERSION__",
+    "better-auth": "^1.6.9",
+    "react": "^19.2.5",
+    "react-dom": "^19.2.5"
+  },
+  "devDependencies": {
+    "@vitejs/plugin-react": "^6.0.1",
+    "vite": "^8.0.10"
+  }
+}