@fourier-labs/harbour 0.1.35-rc.1 → 0.1.36-rc.2

package/README.md

@@ -22,7 +22,7 @@ Then, in an empty folder:
 4. Say "I need Slack" (or Gmail, or the warehouse) — the agent asks IT for access and tells you when it is approved.
 5. Say "ship it" — the agent puts a private preview online and gives you the link; "make it live for everyone" promotes it after you have tried it.
 
-The only step you do yourself is the company sign-in: when the agent runs `harbour login`, your browser opens and you sign in there. You need Node 22+ and Docker Desktop; the agent tells you if either is missing. Full walkthrough: [docs/vibecoding.md](../../docs/vibecoding.md).
+The only step you do yourself is the company sign-in: when the agent runs `harbour login`, your browser opens and you sign in there. You need Node 22+ on a supported Mac; Harbour installs its local database, files and gateway without Docker. Full walkthrough: [docs/vibecoding.md](../../docs/vibecoding.md).
 
 ## Commands
 

package/dist/packages/harbour-cli/src/agent-setup.js

@@ -186,13 +186,13 @@ The person you are working with may not be a developer. They say what they want
 
 ## Getting ready (do this yourself, once per machine and folder)
 
-1. CLI, before \`harbour init\` or anything else: compare the installed CLI with the current release and upgrade it whenever it is behind — a CLI that merely runs is not good enough, only a current one is. \`harbour agent-setup\` prints both versions and says plainly when the installed one is missing or older (its \`--json\` result carries \`cli.upgradeRequired\` and \`cli.remediation\`); without that output, compare \`harbour --version\` with \`npx -y @fourier-labs/harbour --version\` yourself. If either says the installed one is missing or older, run \`npm i -g @fourier-labs/harbour\` and confirm \`harbour --version\` now matches, then continue. Every later command runs the *installed* CLI, so a stale one builds an app that passes every local check and is then refused by the deployment pipeline (\`kit_bundle_incompatible\`) minutes later, with nothing in the app to fix. The kit needs Node 22+ and Docker Desktop running; if Docker is missing, that is the one thing to tell them to install, in one line.
+1. CLI, before \`harbour init\` or anything else: compare the installed CLI with the current release and upgrade it whenever it is behind — a CLI that merely runs is not good enough, only a current one is. \`harbour agent-setup\` prints both versions and says plainly when the installed one is missing or older (its \`--json\` result carries \`cli.upgradeRequired\` and \`cli.remediation\`); without that output, compare \`harbour --version\` with \`npx -y @fourier-labs/harbour --version\` yourself. If either says the installed one is missing or older, run \`npm i -g @fourier-labs/harbour\` and confirm \`harbour --version\` now matches, then continue. Every later command runs the *installed* CLI, so a stale one builds an app that passes every local check and is then refused by the deployment pipeline (\`kit_bundle_incompatible\`) minutes later, with nothing in the app to fix. The kit needs Node 22+ on a supported Mac; it installs and runs its local database, files and gateway without Docker.
 2. Folder: if the current folder has no \`.harbour/\` directory, run \`harbour init --app-root .\` — an empty folder gets a small starter app, an existing Vite + React app gets the kit files added and nothing overwritten. Then read the "Harbour development kit" block in CLAUDE.md / AGENTS.md; it holds the per-app rules.
 3. Sign-in, needed only for company systems and shipping: run \`harbour login\`. It opens the browser and the person finishes the sign-in there — the one step they do themselves; tell them so in one line. If login says the company is not connected yet, ask them for the Harbour link their IT/admin gave them and run \`harbour connect <link>\` first.
 
 ## What they say → what you do
 
-- "run it", "show me", "let me try it" → start \`harbour dev --app-root .\` in the background (it keeps running; the first start pulls images and takes a minute or two). Wait for the line \`Harbour dev is running: http://127.0.0.1:<port>\` and give them that link. Do this unasked as soon as the first check is green — they should always have the link. Locally they are a fixture user; no company sign-in is needed.
+- "run it", "show me", "let me try it" → start \`harbour dev --app-root .\` in the background (it keeps running; the first start downloads the native runtime and takes a minute or two). Wait for the line \`Harbour dev is running: http://127.0.0.1:<port>\` and give them that link. Do this unasked as soon as the first check is green — they should always have the link. Locally they are a fixture user; no company sign-in is needed.
 - "check it", "is it ok?", "is it ready?" → with dev running, \`harbour check --app-root . --json\`, then read \`.harbour/local/check-report.json\`. Failures in the app's code are yours to fix — fix, then check again until it is clean. Run the checks yourself after every change and before every ship, without being asked and without offering them as a choice.
 - "does it work?", and before you report anything as working → open the dev link in your own browser when you have one, press the control you built or changed, and read what the app shows. A green \`harbour check\` is not that proof: it answers governed AI and company systems from fixtures, so the refusals that matter (a field the company's AI route does not accept, a consent the operation does not need, a channel that is not approved) appear only when the control is really pressed. Test rendering, navigation, fixtures and approved reads automatically. In development a Send sends a real email or Slack message: reuse explicit authorization for that bounded test, or ask once if none exists; IT access approval alone is not permission to send. Never ask again for the same authorized test. Before a real integration test, run \`harbour integrations status --app-root . --json\`; explain pending IT approval or missing personal consent before pressing Send, and test the ready parts independently. If you have no browser, say that the button itself is untested.
 - "I need Slack / Gmail / the warehouse / company data" → a fresh \`harbour init\` declares no connection at all, which is why a new app ships with nothing waiting on IT. Never guess a connection, channel, view or mailbox name — a guessed one is refused before IT's queue ever sees it, so nothing appears for IT to approve; use the exact names the person or IT gave you, and if you have none, that is the one question to ask before declaring anything. Before asking, run \`harbour integrations catalog --app-root . --json\` — it lists the company's connections by the exact identifier \`.harbour/integrations.json\` uses, the operations IT allows on each and the approved channels, views and mailboxes per environment — and declare only identifiers and approved names it lists. Declare the connection and only the operations the app really calls in \`.harbour/integrations.json\` (the closed set is in the per-app block), then \`harbour integrations request <connection> --reason "<what the app does with it>" --app-root . --json\`. Request the preview grant in the same turn (\`--environment preview\`) so shipping does not wait on a second IT decision. READY means use it now. PENDING means IT has to approve it: say "IT has to approve this; the app works without it until then", and check later with \`harbour integrations status --app-root . --json\`. A refusal with \`RESOURCE_NOT_APPROVED\` means the channel, view or mailbox is not on the connection yet: IT adds it in the Harbour console under Controls & integrations → API integrations → the provider tile → Configure → Channels (a warehouse view: Controls & integrations → Databases → the source → Views for the environment), and then you run the same request command again. Say "IT has to add <name> to the Slack connection first; the app works without it until then" and nothing more. Never declare a connection the app does not call — every declared one blocks shipping until IT approves it.

package/dist/packages/harbour-cli/src/dev.js

@@ -29,7 +29,7 @@ export async function startDev(root, options) {
         if (sdk === "missing")
             options.output("The kit SDK is not installed: set HARBOUR_KIT_SDK_TARBALL to the bundle's @harbour/app-sdk tarball (or use a bundle with sdk.url).");
         await runtime.writeFiles(options.bundle, ports);
-        options.output("Pulling the kit images by digest (public registry, no login).");
+        options.output("Preparing the kit-managed native runtime (public registry, no login).");
         await runtime.pull(options.bundle);
         options.output("Starting local Harbour services (postgres, storage, one Harbour gateway with the session identities, fixtures and realtime relay).");
         await runtime.up(options.output);

package/dist/packages/harbour-cli/src/kit-bundle.manifest.js

@@ -1,20 +1,20 @@
 export const PUBLISHED_KIT_BUNDLE = {
     "schema": "harbour.kit-bundle/1.0",
-    "kitVersion": "0.1.35",
+    "kitVersion": "0.1.36",
     "sdk": {
         "package": "@harbour/app-sdk",
         "version": "1.1.1",
-        "tarballSha256": "1e0147f601dd45a0402d769aa7ed6b5248b8f5aa79c75dc1fbd6e8303fda5cab",
-        "url": "https://public.ecr.aws/v2/y6t4p3i8/harbour-kit-bundle/blobs/sha256:1e0147f601dd45a0402d769aa7ed6b5248b8f5aa79c75dc1fbd6e8303fda5cab"
+        "tarballSha256": "f499af191dd5a42a41e314cf93b0c7d957e0e1987cbdfc96e7c53eee06d86d25",
+        "url": "https://public.ecr.aws/v2/y6t4p3i8/harbour-kit-bundle/blobs/sha256:f499af191dd5a42a41e314cf93b0c7d957e0e1987cbdfc96e7c53eee06d86d25"
     },
     "images": {
-        "appGateway": "public.ecr.aws/y6t4p3i8/harbour-app-gateway@sha256:8d11d49b9447ee8f4e40d5b2ecd73beaa15048e9e3e47ef0a584546fa8b3fae8",
-        "sessionFixture": "public.ecr.aws/y6t4p3i8/harbour-session-fixture@sha256:d1f7a333294459f95100fd4d74d4033b834856f0a8c6d276360d50af677f30fd"
+        "appGateway": "public.ecr.aws/y6t4p3i8/harbour-app-gateway@sha256:f9b357a326ff88355ad7bec9d88906ba71b9f6264441eb26ded4b3100b37a414",
+        "sessionFixture": "public.ecr.aws/y6t4p3i8/harbour-session-fixture@sha256:30cb03c3e41d459d89f67c01d6877a93287f70013a592284aceb09126bd20de8"
     },
     "nativeRuntime": {
         "darwinArm64": {
-            "url": "https://public.ecr.aws/v2/y6t4p3i8/harbour-kit-bundle/blobs/sha256:9505646bdb1d3566d093f9fa4aa1f3201c9f735fe502752e819bc76cff586c21",
-            "sha256": "9505646bdb1d3566d093f9fa4aa1f3201c9f735fe502752e819bc76cff586c21"
+            "url": "https://public.ecr.aws/v2/y6t4p3i8/harbour-kit-bundle/blobs/sha256:1e3ad4ffb046c3d9a79919dd645b45e478cc0b9a0ccec7ded6dadbca39b093b6",
+            "sha256": "1e3ad4ffb046c3d9a79919dd645b45e478cc0b9a0ccec7ded6dadbca39b093b6"
         }
     },
     "brief": {

package/dist/packages/harbour-cli/src/version.js

@@ -1 +1 @@
-export const CLI_VERSION = "0.1.35-rc.1";
+export const CLI_VERSION = "0.1.36-rc.2";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fourier-labs/harbour",
-  "version": "0.1.35-rc.1",
+  "version": "0.1.36-rc.2",
   "description": "Harbour productionisation helper",
   "type": "module",
   "bin": {
@@ -37,7 +37,7 @@
   "harbour": {
     "kitBundle": {
       "repository": "public.ecr.aws/y6t4p3i8/harbour-kit-bundle",
-      "version": "0.1.35"
+      "version": "0.1.36"
     }
   }
 }