@owlmeans/viable-common 0.0.26 → 0.0.27

package/README.md

@@ -21,7 +21,7 @@ filesystem, no inference SDK. It is safe to import from a browser bundle.
 ## Installation
 
 ```bash
-bun add @owlmeans/viable-common@^0.0.26
+bun add @owlmeans/viable-common@^0.0.27
 ```
 
 ## Rules worth knowing before you change something
@@ -39,7 +39,7 @@ means "inherit" has no other spelling. `tests/convert.spec.ts` walks every expor
 both faults, and for draft-04 tuple `items`.
 
 **A field that crosses a version skew carries no `enum`.** A connector is installed with
-`npx -y @owlmeans/viable-mcp@^0.1.18-rc.22` and talks to a separately deployed platform, so an executor kind it
+`npx -y @owlmeans/viable-mcp@^0.1.18-rc.23` and talks to a separately deployed platform, so an executor kind it
 sends must remain an unused capability on an older platform rather than a refused session.
 
 **A ceiling exists once.** The inquiry answer cap here equals `DEFAULT_INQUIRY_ANSWER_CHARS` in

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/viable-common",
-  "version": "0.0.26",
-  "generatedAt": "2026-09-21T21:54:22.967Z",
+  "version": "0.0.27",
+  "generatedAt": "2026-09-22T09:20:40.384Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/agent-presentation/SKILL.md

@@ -6,7 +6,7 @@ description: Shared, runtime-free taxonomy for presenting OwlMeans Viable agent
 
 # Agent output presentation
 
-**Install:** `"@owlmeans/viable-common": "^0.0.26"` in `dependencies`
+**Install:** `"@owlmeans/viable-common": "^0.0.27"` in `dependencies`
 
 `@owlmeans/viable-common`'s `agent/presentation.ts` owns the browser-safe vocabulary for agent
 output. Keep the server and every client on `classifyAgentMessage()`; consumers may refine a

package/agent-meta/skills/viable-common/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/viable-common
 
 **Layer:** Cross-cutting domain (contracts only)
-**Install:** `"@owlmeans/viable-common": "^0.0.26"` in `dependencies`
+**Install:** `"@owlmeans/viable-common": "^0.0.27"` in `dependencies`
 **Subpaths:** `.` · `./slot` · `./connect` · `./convert` · `./integrity`
 **Runtime-free:** no `@langchain/*`, no filesystem, no Ajv at run time (a devDependency, for the
 tests that compile the schemas). It depends on `@owlmeans/planning`, `@owlmeans/resource`,
@@ -253,7 +253,7 @@ code, never as `minItems`/`maxItems`. The descriptions are what the planning mod
 state each field's purpose and bounds; `gate.target` is filled by code and described as such.
 
 **A field that crosses a version skew carries no `enum`.** Users run
-`npx -y @owlmeans/viable-mcp@^0.1.18-rc.22` (the moving prerelease tag) against a separately deployed
+`npx -y @owlmeans/viable-mcp@^0.1.18-rc.23` (the moving prerelease tag) against a separately deployed
 platform, so `ConnectCapabilitiesSchema.executors.items`
 is a bare string: a newer executor kind must stay an unused capability on an older platform, never
 a refused session. Apply the same reasoning to anything else a newer connector may send an older
@@ -346,8 +346,10 @@ theme, a brand palette, gradients; the product's subject matter is not a request
 `tests/skills.spec.ts` pins both texts against drifting back.
 
 `ViableSkill.LandingGate` teaches the gate-worthy story, the gate card, the synchronous handoff
-(`writeLandingHandoff` then `useLogin(target)` in one gesture) and the full-scale screen that reads
-and clears it. Every `ViableSkill` member has a body in `VIABLE_SKILLS` and a weight in
+(`useLandingStart(target)` from the seed's `@/lib/handoff`: write, then navigate when signed in or
+start the plain sign-in; the guest home's `useLandingContinuation` sends the visitor on after
+sign-in — never `useLogin(target)`, whose continuation lands on the guarded screen) and the
+full-scale screen that reads and clears it. Every `ViableSkill` member has a body in `VIABLE_SKILLS` and a weight in
 `SKILL_ORDER`: the prompt service skips an alias it cannot resolve, so a missing body is a rule no
 model ever receives.
 

package/build/skills/catalogue.js

@@ -825,24 +825,24 @@ there is no gate and the hero keeps its buttons — a correct answer, not a fail
 **The handoff.** The button carries the guest's choices across sign-in in \`sessionStorage\`,
 through \`@/lib/handoff\` — never in the URL, never in a cookie, never through the server:
 
-    import { useLogin } from '@owlmeans/client-iam'
-    import { writeLandingHandoff } from '@/lib/handoff'
+    import { useLandingStart } from '@/lib/handoff'
 
-    const [, login] = useLogin(target)
-    const start = () => {
-      writeLandingHandoff(target, { picks })
-      login()
-    }
-    <button type="button" className="cta-btn" onClick={start}>{cta}</button>
+    const start = useLandingStart(target)
+    <button type="button" className="cta-btn" onClick={() => start({ picks })}>{cta}</button>
 
 - \`target\` is the ALIAS of the story's own full-scale screen in the user area — the prop the guest
-  home passes — never a URL. \`useLogin(target)\` returns \`[path, handler]\`, and the handler
-  brings the person to \`target\` once they are signed in.
-- The click handler is SYNCHRONOUS: write, then call the handler, in the same gesture. A sign-in
-  that has to open a window is eaten by the popup blocker once anything has been awaited first.
-
-      onClick={async () => { await saveDraft(picks); login() }}     // WRONG — the gesture is gone
-      href={'/frontoffice/recipes?picks=' + picks.join(',')}         // WRONG — a URL, the picks in it, no sign-in
+  home passes — never a URL.
+- \`useLandingStart(target)\` is the whole button: it writes the handoff, then navigates to
+  \`target\` when the visitor is already signed in, or starts the ordinary sign-in otherwise. After
+  sign-in the guest home's \`Hero\` (\`useLandingContinuation\`) sends the visitor on to \`target\`.
+- NEVER \`useLogin(target)\` for the gate: its continuation navigates straight to the guarded screen,
+  which answers a signed-out visitor with "Sign in required", and that card's own sign-in lands on the
+  home page — the full-scale screen is never reached.
+- The handler \`useLandingStart\` returns is SYNCHRONOUS, and the click calls it in the same gesture.
+  A sign-in that has to open a window is eaten by the popup blocker once anything has been awaited.
+
+      onClick={async () => { await saveDraft(picks); start({ picks }) }}  // WRONG — the gesture is gone
+      href={'/frontoffice/recipes?picks=' + picks.join(',')}               // WRONG — a URL, the picks in it, no sign-in
 
 **The full-scale screen** — the story's own screen in the user area — reads the handoff once in its
 view model, pre-fills from it, says so in one line, and clears it:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/viable-common",
-  "version": "0.0.26",
+  "version": "0.0.27",
   "license": "MIT",
   "description": "Runtime-free contracts of the OwlMeans Viable platform — the analysis, design and metadata shapes of a generated project, its target-shape manifest, the slot command vocabulary, the connector protocol and the conversion vocabulary.",
   "type": "module",

package/src/skills/catalogue.ts

@@ -856,24 +856,24 @@ there is no gate and the hero keeps its buttons — a correct answer, not a fail
 **The handoff.** The button carries the guest's choices across sign-in in \`sessionStorage\`,
 through \`@/lib/handoff\` — never in the URL, never in a cookie, never through the server:
 
-    import { useLogin } from '@owlmeans/client-iam'
-    import { writeLandingHandoff } from '@/lib/handoff'
+    import { useLandingStart } from '@/lib/handoff'
 
-    const [, login] = useLogin(target)
-    const start = () => {
-      writeLandingHandoff(target, { picks })
-      login()
-    }
-    <button type="button" className="cta-btn" onClick={start}>{cta}</button>
+    const start = useLandingStart(target)
+    <button type="button" className="cta-btn" onClick={() => start({ picks })}>{cta}</button>
 
 - \`target\` is the ALIAS of the story's own full-scale screen in the user area — the prop the guest
-  home passes — never a URL. \`useLogin(target)\` returns \`[path, handler]\`, and the handler
-  brings the person to \`target\` once they are signed in.
-- The click handler is SYNCHRONOUS: write, then call the handler, in the same gesture. A sign-in
-  that has to open a window is eaten by the popup blocker once anything has been awaited first.
-
-      onClick={async () => { await saveDraft(picks); login() }}     // WRONG — the gesture is gone
-      href={'/frontoffice/recipes?picks=' + picks.join(',')}         // WRONG — a URL, the picks in it, no sign-in
+  home passes — never a URL.
+- \`useLandingStart(target)\` is the whole button: it writes the handoff, then navigates to
+  \`target\` when the visitor is already signed in, or starts the ordinary sign-in otherwise. After
+  sign-in the guest home's \`Hero\` (\`useLandingContinuation\`) sends the visitor on to \`target\`.
+- NEVER \`useLogin(target)\` for the gate: its continuation navigates straight to the guarded screen,
+  which answers a signed-out visitor with "Sign in required", and that card's own sign-in lands on the
+  home page — the full-scale screen is never reached.
+- The handler \`useLandingStart\` returns is SYNCHRONOUS, and the click calls it in the same gesture.
+  A sign-in that has to open a window is eaten by the popup blocker once anything has been awaited.
+
+      onClick={async () => { await saveDraft(picks); start({ picks }) }}  // WRONG — the gesture is gone
+      href={'/frontoffice/recipes?picks=' + picks.join(',')}               // WRONG — a URL, the picks in it, no sign-in
 
 **The full-scale screen** — the story's own screen in the user area — reads the handoff once in its
 view model, pre-fills from it, says so in one line, and clears it:

package/tests/skills.spec.ts

@@ -97,10 +97,12 @@ describe('viable-common catalogue — the house style', () => {
 
     expect(body).toContain('data-home-gate')
     expect(body).toContain('aria-pressed')
-    expect(body).toContain('writeLandingHandoff(target')
+    expect(body).toContain('useLandingStart(target)')
+    expect(body).toContain('useLandingContinuation')
     expect(body).toContain('readLandingHandoff')
     expect(body).toContain('clearLandingHandoff()')
-    expect(body).toContain("useLogin(target)")
+    // Named only as the thing NOT to do: its continuation lands on the guarded screen.
+    expect(body).toContain('NEVER `useLogin(target)`')
     expect(body).toContain('SYNCHRONOUS')
     expect(body).toContain('WRONG')
     expect(body).not.toContain('${')