website-build-skill 0.1.4 → 0.1.6

package/skills/website-build-skill/SKILL.md

@@ -40,7 +40,8 @@ true as of the date of your ask, not from what its model happens to remember.
 This question is for the human at install, displayed by the README or installer.
 Follow the recorded --solo / --team choice or the option named in the user's setup prompt.
 Do not repeat it during the method. If no choice exists, return to the install entrypoint.
-Option 2 requires Claude Code, Codex, Hermes, Antigravity, or Grok Bot; its setup checks actual workers.
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+Option 2 uses Claude Code, Codex, Hermes, Antigravity, or Grok Bot; the human checks each session.
 Both options use the same gates. Solo review is INTERNAL until a different family reviews.
 
 Read prompts/00-start.md to give Researcher the request and available tools.
@@ -92,7 +93,7 @@ The graphics original is inactive provenance, excluded from every active stage r
 | Protect | Builder | 09-security-headers | security.md |
 | Challenge | Different-family Reviewer | 10-adversarial-pre-ship | research.md AD09; [code-quality.md](checklists/code-quality.md); ship.md SH01-SH03 |
 | Ship | Coordinator acceptance, Builder release | 11-ship-and-verify | ship.md, pre-promotion then live checks |
-| Team setup | Human or installer | 12-web-design-team | Seven route acknowledgements; no downstream work yet |
+| Team setup | Human opens sessions and carries handoffs | 12-web-design-team | Seven route acknowledgements; no downstream work yet |
 
 Use full filenames and asset order from manifest.json; the table abbreviates prompt suffixes.
 For limited audits, load the relevant current research and checks without inventing redesign work.

package/skills/website-build-skill/manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "packageVersion": "0.1.4",
+  "packageVersion": "0.1.6",
   "skillName": "website-build-skill",
   "pathBase": "All asset paths resolve from this manifest directory; runtime paths resolve in the authorized user project.",
   "assets": [
@@ -17,7 +17,7 @@
         "skill-zip",
         "native-skill"
       ],
-      "sha256": "ed1c909f9946de0fa7a43364c84efc837b6644c0dc8334b81ddfaf031db156e1"
+      "sha256": "71cb5b229d68ae1b91a11d4168c6093a88d0c0f7da2dbcab0c933cb6a333c81b"
     },
     {
       "path": "manifest.json",
@@ -45,7 +45,7 @@
         "skill-zip",
         "native-skill"
       ],
-      "sha256": "d5ed2a92d5bd7071895658ebbf4d7d696aeddb3735aa8d9153d0405c517f7b9c"
+      "sha256": "9de537723108ad71b608c467d78c7ba6edb54880d0429f5321d490cba9c900cb"
     },
     {
       "path": "prompts/01-website-deep-research.md",
@@ -225,7 +225,7 @@
         "skill-zip",
         "native-skill"
       ],
-      "sha256": "58a53b49b1da1039195d0ecaa24dff296668d9c4c4a52545d40836ddf8d6d388"
+      "sha256": "a1b1460deea3520d25245d805521019f758b905b97e73ac97e7020cead861837"
     },
     {
       "path": "prompts/13-coding-research.md",

package/skills/website-build-skill/prompts/00-start.md

@@ -15,10 +15,11 @@ Do not repeat the install question mid-method. If no choice is recorded, return
 its install entrypoint to the human before starting work.
 
 TEAM SETUP
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
 - Read roles/researcher.md, roles/coordinator.md, roles/designer.md, roles/graphics.md, roles/builder.md,
   roles/optimizer.md, and roles/reviewer.md.
-- Run prompts/12-web-design-team.md to establish workers, ownership, and handoffs.
-- Installer or human checks routes during setup; create Researcher first. Coordinator
+- Follow prompts/12-web-design-team.md while the human opens the sessions and carries handoffs.
+- The human checks session references during setup and opens Researcher first. Coordinator
   records families and working readiness after the research gate passes.
 - Role labels within one conversation are option 1; if separate workers are unavailable,
   say so, record SOLO, and continue below. Missing independent review alone blocks

package/skills/website-build-skill/prompts/12-web-design-team.md

@@ -4,6 +4,7 @@ Never ask the user for the date or infer it from model knowledge. Apply the
 same source, two-date, freshness, reuse, and blocked-gate rules to this stage.
 
 Run option 2, Give me the team, using the human's recorded install choice.
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
 Needs Claude Code, Codex, Hermes, Antigravity, or Grok Bot. Follow the setup line for that host.
 
 Every agent runs its own research pass before it touches your site, so it works from what is
@@ -16,22 +17,21 @@ SET UP
 - Read roles/researcher.md first, then roles/coordinator.md, roles/designer.md,
   roles/graphics.md, roles/builder.md, roles/optimizer.md, roles/reviewer.md,
   and templates/handoff.yaml. Use each complete body, not these short summaries.
-- Create or identify Website Researcher first, then Website Coordinator,
+- The human opens Website Researcher first, then Website Coordinator,
   Website Designer, Website Graphics, Website Builder, Website Optimizer, and
-  Website Reviewer as separate sessions, Bots, or terminals. Parent may coordinate
-  only after the research gate. Use supported setup mechanisms, not invented imports.
-- Installer or human checks routes and obtains seven setup acknowledgements.
+  Website Reviewer as separate sessions, Bots, or terminals. Coordinator works
+  only after the research gate. Use available session controls and complete role files.
+- The human checks each session reference and obtains seven setup acknowledgements.
   These confirm receipt of instructions, not permission to start downstream work.
 - A role label in one conversation is option 1. Record SOLO and use prompts/00-start.md
   if separate workers cannot be reached. A same-family team remains a team but
   cannot pass independent review. Respect host concurrency limits.
-- Antigravity setup uses generated agent definitions and per-role tool declarations;
-  Hermes setup uses the verified definition branch or generated session packets and
-  bundle alias. Read the host adapter and receipt; pending discovery, trust, tools,
-  or independent review checks cannot be reported as a ready team.
+- Read the host adapter and receipt. The installer supplies role files and bundles;
+  the human opens sessions, checks trust and tools, and supplies each worker's files.
+  Pending discovery, trust, tools or independent review checks remain explicit limits.
 - Supply the request, authorized workspace, source assets, and tools to Researcher.
-  All other roles wait. Use the manual fallback in the team bundle if setup cannot
-  be automated; actual package integration remains UNVERIFIED until tested.
+  All other roles wait. Carry the complete packets using the manual setup below;
+  actual host loading remains UNVERIFIED until tested.
 
 RESEARCHER
 - Own site-work/research/library/ and handoffs/researcher/; own both research resources.
@@ -114,9 +114,9 @@ Never report a measured, saved, installed, or deployed result without evidence.
 Apply checklists/research.md before downstream dispatch and checklists/ship.md before release.
 
 PORTABLE MANUAL SETUP
-Use this fallback when native adapters or generated bundles are not supplied.
-Native loading, automatic worker creation, routing, tool enforcement and different-family
-availability are UNVERIFIED until the actual host/session checks succeed.
+Use this setup for TEAM on every host. You open each session and carry every handoff.
+Host loading, file access, tool enforcement and different-family availability remain
+UNVERIFIED until the actual host/session checks succeed.
 A missing host adapter does not authorize inventing a native file format or import API.
 
 1. Open the host's verified worker/session creation surface, if available.
@@ -128,8 +128,8 @@ A missing host adapter does not authorize inventing a native file format or impo
    with evidence, tools, inaccessible files, and owned paths. Keep downstream work pending.
 5. Give Reviewer a read-only candidate packet or verified read-only session. Broad
    inherited tools do not become restricted because role prose says read-only.
-6. Verify a bounded setup message reaches each intended route through supported controls.
-   When group automation is absent, the human can relay addressed packets and attachments.
+6. Deliver a bounded setup message to each session yourself. Relay addressed packets
+   and attachments, and verify each receiving worker can open them.
 7. Give the user's actual request, authorized workspace, assets and constraints to
    Researcher alone. It establishes ASK DATE and completes the library and gate first.
 8. Relay its complete passing receipt and readable library to Coordinator. Coordinator
@@ -138,7 +138,7 @@ A missing host adapter does not authorize inventing a native file format or impo
 Preserve seven acknowledgements separately from research and work-readiness receipts.
 A text-only group requires direct image attachments to each receiving visual reviewer.
 Inaccessible files or routes keep the relevant handoff BLOCKED.
-No automatic creation support means a manual setup limit, not a claimed ready team.
+Completed file installation means the files are available; session setup is the human's next step.
 No separate workers means SOLO; no independent family means independent review BLOCKED.
 Never invent a platform capability to fill a setup gap.
 

package/src/bundle.mjs

@@ -140,6 +140,7 @@ export function generated(root) {
   index += '- [Installer](docs/INSTALLER.md): headless setup, destinations, receipts, exit codes and uninstall\n';
   index += '- [Compatibility](docs/COMPATIBILITY.md): host setup routes and the evidence for each\n';
   index += '- [Documentation](docs/README.md): method, tips, provenance and evaluation\n\n';
+  index += "TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.\n\n";
   index += '## Active sources\n\n';
   for (const asset of m.assets.filter(a => a.active)) index += `- [${asset.path}](${CORE}/${asset.path}): ${describe(root, asset)}\n`;
   index += '\n## Bundles\n\n';

package/src/install.mjs

@@ -1,5 +1,5 @@
 import fs from 'node:fs';
-import { resolve, relative, dirname, basename, sep } from 'node:path';
+import { resolve, relative, dirname, basename, join, sep } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { randomUUID } from 'node:crypto';
 import { CORE, files, owned, digest } from './bundle.mjs';
@@ -59,6 +59,22 @@ export function safePath(root, name) {
 const receiptName = '.website-build-skill-receipt.json';
 const result = (code, message) => ({ code, message });
 
+function canonicalReceipt(path, root, destination, outputRoot) {
+  const boundaries = [destination, outputRoot].filter(Boolean);
+  // Resolve the user's root spelling, but inspect its suffix before using the canonical
+  // receipt parent: otherwise a planted link below an output or destination root disappears.
+  // An ancestor that resolves anywhere INSIDE a root (an alias to a subdirectory, not only
+  // to the root itself) is walked from that root, so no link below it is skipped.
+  for (let parent = dirname(path); ; parent = dirname(parent)) {
+    const base = canonical(parent);
+    for (const boundary of boundaries) {
+      if (inside(boundary, base)) safePath(boundary, join(relative(boundary, base), relative(parent, path)));
+    }
+    if (dirname(parent) === parent) break;
+  }
+  return safePath(root, resolve(root, basename(path)));
+}
+
 function validate(request) {
   if (!Object.hasOwn(targets, request.target)) throw Error('Unknown or missing target');
   if (!['solo', 'team'].includes(request.mode)) throw Error('Mode must be solo or team');
@@ -240,11 +256,12 @@ export function install(request = {}) {
       destination = resolve(project, targets[request.target]);
       receiptPath = resolve(request.receipt ?? resolve(destination, receiptName));
       receiptRoot = request.receipt ? canonical(dirname(receiptPath)) : destination;
-      outputRoot = request.outputDir === undefined ? null : canonical(request.outputDir);
     }
+    outputRoot = request.outputDir === undefined ? null : canonical(request.outputDir);
   } catch (error) { return result(2, error.message); }
-  if (request.uninstall) return uninstall(request, destination, receiptPath, receiptRoot);
   try {
+    if (request.receipt) receiptPath = canonicalReceipt(receiptPath, receiptRoot, destination, outputRoot);
+    if (request.uninstall) return uninstall(request, destination, receiptPath, receiptRoot);
     safePath(project, targets[request.target]);
     if (request.receipt) safePath(receiptRoot, receiptPath);
     if (inside(destination, receiptPath) && receiptPath === destination) throw Error('Receipt collides with destination');
@@ -274,7 +291,7 @@ export function install(request = {}) {
       if (info && entry.wrote) conflicts.push(entry.path);
     }
     if (conflicts.length) return result(3, `Preflight conflicts; nothing written:\n${conflicts.join('\n')}`);
-  } catch (error) { return result(3, `Preflight refused; nothing written: ${error.message}`); }
+  } catch (error) { return request.uninstall ? result(2, error.message) : result(3, `Preflight refused; nothing written: ${error.message}`); }
   const receipt = {
     schemaVersion: 1, package: packageInfo, date: new Date().toISOString(), mode: request.mode,
     target: request.target, scope: request.scope ?? 'project', destination, outputRoot,