website-build-skill 0.1.4 → 0.1.6

package/docs/bundles/prompts.md

@@ -43,10 +43,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
@@ -890,6 +891,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
@@ -902,22 +904,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.
@@ -1000,9 +1001,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.
@@ -1014,8 +1015,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
@@ -1024,7 +1025,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/docs/bundles/team.md

@@ -29,6 +29,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
@@ -41,22 +42,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.
@@ -139,9 +139,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.
@@ -153,8 +153,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
@@ -163,7 +163,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.
 
@@ -1681,6 +1681,8 @@ Never report a measured, saved, installed, or deployed result without evidence.
 
 ## Manual fallback
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first. This manual relay is the TEAM workflow.
+
 **Prepare the files and workspace**
 
 - Get the complete `docs/bundles/team.md`, `method.md`, `prompts.md`, `playbooks.md`, and `checklists.md` from the same release. The team bundle contains the seven complete role bodies and this guide; the prompts bundle contains active prompts.
@@ -1703,7 +1705,7 @@ Never report a measured, saved, installed, or deployed result without evidence.
 **Connect the group and verify its routes**
 
 - If your account exposes group creation, create `Website Design` and add the seven saved Bots in the same order, Researcher first. Record the actual route for each. Verify one bounded setup message reaches the intended recipient using the host's documented addressing controls.
-- If group routing or automated handoff is unavailable, use separate Bot chats and relay each handoff and its attachments manually. Keep distinct workers on separate routes; separate workers need separate routes, and labels inside one chat stay one worker. Ordinary single-chat work uses SOLO.
+- Use separate Bot chats and relay each handoff and its attachments manually, including when the account offers a group view. Keep distinct workers on separate routes; separate workers need separate routes, and labels inside one chat stay one worker. Ordinary single-chat work uses SOLO.
 - If group messages are text-only, attach mockups and assets directly to the receiving Bot. Image review needs the Bot to open the image itself; a text path alone gives it only the path, so confirm the receiving Bot can inspect the image directly.
 - Give Coordinator this complete contract after replacing each angle-bracket route with the real saved Bot/chat reference. Unresolved placeholders keep setup incomplete.
 
@@ -1735,7 +1737,7 @@ with Builder's route/content inputs. Send the fixed final candidate to Reviewer
 only after pre-review gates pass. Different-family review remains mandatory.
 Read every returned artifact. Preserve Reviewer returns unchanged. Use every field
 in templates/handoff.yaml and record gate acceptance only in site-work/status.md.
-If routing fails, return the complete addressed packet for me to relay manually.
+Return every complete addressed packet for me to relay manually.
 ```
 
 **Trigger the first work handoff**
@@ -1756,11 +1758,11 @@ leave the research gate BLOCKED. If you cannot save files, return named file bod
 for me to save and reattach; wait for read-back before passing the disk gate.
 Pass only when the saved library covers every touched domain and every claim we
 will act on has an opened source URL, a publication/update date or explicit unknown, and an access date on or after the ASK DATE. Read back the actual saved files before confirming persistence.
-Then send research-to-coordinator to <actual Coordinator route> using all handoff
-fields and readable artifacts. No other role starts before this research gate.
+Then return research-to-coordinator addressed to <actual Coordinator route> for me
+to relay, using all handoff fields and readable artifacts. No other role starts before this research gate.
 ```
 
-- First receipt: Researcher supplies `site-work/handoffs/researcher/research-<revision>.yaml` and its library. If automatic delivery fails, copy the whole receipt and attach the library to Coordinator yourself.
+- First receipt: Researcher supplies `site-work/handoffs/researcher/research-<revision>.yaml` and its library. Copy the whole receipt and attach the library to Coordinator yourself.
 - First acceptance: Coordinator opens the files, checks coverage and source dates, and writes PASS or BLOCKED in `site-work/status.md`. Only PASS releases downstream scope handoffs.
 - First design: Designer and Graphics read their named library files, return learning/top-up receipts, and apply their domain checklists. They open the evidence behind the research summary before starting.
 - Persistence: preserve the files and receipts, and reattach the current revision in each new session. Carry state in the saved files, since a Bot may not remember a group chat. A durable-memory proposal remains pending until an actual supported save is read back.
@@ -1769,6 +1771,8 @@ fields and readable artifacts. No other role starts before this research gate.
 ## Artifact ownership roster
 
 ```yaml
+# TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+# This roster records ownership and handoff fields for the human to relay.
 schema_version: 1
 team: website-design-team
 coordinator: coordinator

package/docs/evaluation/host-gate.md

@@ -0,0 +1,129 @@
+# Manual host gate
+
+Status: NOT RUN. This document defines the work behind the explicit live-host skips.
+Live host behaviour is verified by receipts, not by `npm test`. The suite reports these
+items as skipped until a contributor supplies the required observations.
+
+## Automated distribution boundary
+
+Run from the package checkout:
+
+```sh
+node --test test/packed-artifact.test.mjs
+npm run check
+npm test
+```
+
+The packed-artifact test packs this revision, installs the tarball into a temporary
+consumer's `node_modules`, resolves the installed bin there, and runs SOLO and TEAM
+against empty destinations. It checks file trees, bytes, receipts and uninstall.
+The repository check workflow schedules it on `ubuntu-latest`, `macos-latest` and
+`windows-latest`. A configured matrix is a check to run; its results require CI evidence.
+The stable Repository checks job requires every matrix entry to succeed.
+
+Host discovery, upload controls, model behaviour and session permissions need the manual
+checks below. The repository currently builds bundles and an npm tarball; it has no ZIP
+production step. GitHub source archives and manually prepared skill ZIPs use the ZIP gate.
+
+## Hosts and operating systems
+
+Run each applicable item on the exact host, client version and OS whose compatibility
+claim you intend to make. Use Linux, macOS and Windows for any claim covering all three;
+keep unavailable host/OS combinations UNVERIFIED with a reason. A browser trial also
+records browser version and account controls available during that trial.
+
+| Host | Setup and loading instructions | Modes to observe |
+| --- | --- | --- |
+| Claude Code | [Adapter](../../adapters/claude-code.md) | SOLO and separately TEAM |
+| Codex | [Adapter](../../adapters/codex.md) | SOLO and separately TEAM |
+| Hermes | [Adapter](../../adapters/hermes.md), including explicit alias and trust checks | SOLO and separately TEAM |
+| Antigravity | [Adapter](../../adapters/antigravity.md) | SOLO and separately TEAM |
+| Grok Bot | [Adapter](../../adapters/grok.md), including attachment and manual relay controls | SOLO and separately TEAM |
+| Claude Desktop | [Adapter](../../adapters/claude-desktop.md), including skill ZIP upload where exposed | SOLO; record any separate-session TEAM trial separately |
+| ChatGPT Project | [Adapter](../../adapters/chatgpt-project.md) | SOLO; record any separate-session TEAM trial separately |
+| Custom GPT | [Adapter](../../adapters/custom-gpt.md) | SOLO; record any separate-session TEAM trial separately |
+| Generic file-reading agent | [Adapter](../../adapters/agents-md.md); name the actual client | SOLO; record any separate-session TEAM trial separately |
+
+TEAM installs seven workers' files in one command; you open each session yourself and
+carry the handoffs between them. Researcher goes first. Retain all seven setup
+acknowledgements separately from the research receipt and later work receipts.
+
+## Skipped item: live AD01-AD09 behaviour
+
+Test title: `Live AD01-AD09 behavior: ladder evidence, clock override, no-search blockage, stale claims, derived floors and multi-day expiry`.
+
+1. Use a fresh synthetic project on each claimed host/OS above. Follow the
+   [host trial](host-trial.md) to install, explicitly load the skill and record tool access.
+2. Run every case in `test/fixtures/ask-date-cases.md` from the matching source checkout
+   (test fixtures are checkout-only files).
+   Follow [AD01-AD09](../../skills/website-build-skill/checklists/research.md) and the
+   [ASK DATE rule](../../skills/website-build-skill/playbooks/research-and-memory.md#ask-date-rule)
+   for the expected boundary, including the independent AD09 review.
+3. Record the supplied input, actual tool evidence and observed response for each case.
+   Retain date ladder failures, conflicting clock evidence, absent search, stale claims,
+   derived floors and multi-day expiry observations. A fixture's expected answer is a
+   criterion, not an observation. Identify simulated tools separately from live tools;
+   a simulation cannot establish the live capability it replaces.
+4. Save scope, library, source receipts, gate output and transcript excerpts. Mark each
+   AD check PASS, FAIL, BLOCKED or NOT APPLICABLE with its evidence and reason. A missing
+   different-family Reviewer leaves AD09 BLOCKED.
+
+## Skipped item: per-host npm and ZIP distribution
+
+Test title: `Planned distribution: fresh npm tarball and ZIP installation on each claimed operating system and host`.
+The npm file-install portion is automated above; this skip covers actual host loading
+from that installation and ZIP extraction/upload on the host/OS combinations claimed.
+
+1. From the revision being evaluated, run `npm pack --json --ignore-scripts --pack-destination <existing-temp-directory>`.
+   Save the JSON report and the tarball digest. In a separate empty consumer, run
+   `npm init -y`, then `npm install --ignore-scripts --no-audit --no-fund <absolute-tarball-path>`.
+2. Run the consumer's installed bin, substituting the adapter target and a fresh absolute
+   trial directory. Repeat with `--team` in another empty trial directory:
+
+   ```sh
+   node node_modules/website-build-skill/bin/website-build-skill.mjs --solo --target codex --dir <trial-directory> --yes
+   ```
+
+   Compare receipt paths and hashes with the disk. Open the actual host in the trial
+   directory and follow its loading check. Record explicit file reads separately from
+   native discovery. Verify accessible assets, preserved existing instructions and
+   error/conflict behaviour in separate synthetic fixtures.
+3. For a GitHub source ZIP, download the archive for that exact commit, record its URL
+   and digest, extract it into an empty directory and follow the adapter's manual copy
+   or bundle-attachment steps. Verify manifest hashes and loaded resources.
+4. For a skill-upload ZIP, create an archive containing one complete
+   `website-build-skill/` directory from `skills/website-build-skill/`, with manifest and
+   relative assets. Record the packaging command/tool version, layout and digest.
+   Upload using the actual account controls described by the adapter and confirm each
+   loaded resource. Record absent upload controls as BLOCKED for that route. Source
+   archives and skill-upload ZIPs are distinct artifacts and need separate results.
+5. Save installer output, receipt, installed file/digest inventory, exact invocation,
+   host transcript and observed limits. Use the [full trial](host-trial.md) separately
+   before making a website-outcome claim.
+
+## Receipt and acceptance
+
+Copy [receipt-template.json](receipt-template.json) into the private trial workspace.
+Fill its fields from observations, including:
+
+- Identity: trial ID, package commit, artifact filename and SHA-256, host/client version,
+  OS/version, runtime and actual model family, mode, invocation and start/end times.
+- Commands: exact commands, working-directory roles, exit codes and relevant output.
+- Boundaries: each skipped item and AD check attempted, expected and observed behaviour,
+  status, and links to transcript excerpts, installed receipts and supporting files.
+- Negative trials: missing tools, conflicts and other failures actually exercised.
+- Review: candidate digest, actual reviewer family, findings and reproduced dispositions.
+- Limits: untested host/OS/mode combinations and unavailable controls; reproduction steps.
+
+Add artifact metadata to `artifacts` and per-case observations to `boundaries`; preserve
+unknown values as null. Sanitize private paths, account identifiers and credentials.
+Save the receipt as `docs/evidence/host-gate-<trial-id>.json` and its supporting artifacts
+under `docs/evidence/host-gate-<trial-id>/`. A reviewer reopens those artifacts before
+accepting the result. Keep failed and blocked receipts alongside successful ones.
+
+Each skipped item advances to either a real executable test for the behaviour it can
+assert, or a linked, reviewed receipt for the exact host/OS/mode observed. A receipt may
+be linked beside a retained skip for combinations still awaiting trials. A skipped test
+is never converted to a pass by editing its label, removing `skip`, or adding an empty
+passing body. `npm test` alone establishes no live-host result. Promote compatibility
+only for the observed scope under the [host-trial evidence rules](host-trial.md#publish-evidence-and-promote-narrowly).

package/docs/evaluation/host-trial.md

@@ -2,6 +2,8 @@
 
 Status: NOT RUN. This protocol is an acceptance test, not evidence of host support.
 A passing repository test suite or a copied skill folder cannot promote this status.
+Use the [manual host gate](host-gate.md) for the suite's live-host skips, per-OS loading
+checks, ZIP trials and required receipts.
 
 ## Scope and authority
 
@@ -14,7 +16,8 @@ Use a local preview. Production release and live-host checks remain BLOCKED.
 The operator supplies the visual selection and a separate model family for review.
 If either is unavailable, record the exact boundary reached; do not manufacture a PASS.
 The first useful milestone is one complete SOLO local-preview trial on one named host.
-TEAM requires a separate trial with seven observed routes and cannot inherit that result.
+TEAM requires a separate trial with seven sessions the human opens and handoffs they
+carry, with Researcher first; it cannot inherit the SOLO result.
 
 ## Prepare and invoke