website-build-skill 0.1.4 → 0.1.6

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "website-build-skill",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "A skill pack that teaches your AI current website-building expertise: research, design, code, accessibility, performance, search and security.",
   "author": {
     "name": "website-build-skill contributors"

package/CHANGELOG.md

@@ -6,6 +6,31 @@ Version policy: [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html)
 
 ## [Unreleased]
 
+## [0.1.6] - 2026-09-24
+
+### Added
+
+- Dated native-loading receipt for the Grok Build CLI 1.0.40 (SOLO, macOS, trusted folder, 2026-09-24) in `docs/evidence/`, linked from compatibility and the Grok adapter ([#15](https://github.com/aunysillyme/website-build-skill/issues/15)).
+
+### Changed
+
+- The Grok adapter says to trust the project folder: Grok Build offers project skills only in a trusted folder, found during the trial. Grok Bot (the Bots app) is named separately as still awaiting its trial.
+
+## [0.1.5] - 2026-09-24
+
+### Added
+
+- Packed consumer-install checks for SOLO and TEAM on a Linux, macOS and Windows CI matrix, plus explicit live-host skips and a manual receipt gate ([#16](https://github.com/aunysillyme/website-build-skill/issues/16)).
+- Dated native-loading receipts for Claude Code 2.1.281 and Codex CLI 0.154.0 (SOLO, macOS, 2026-09-24) in `docs/evidence/`, linked from compatibility and both adapter pages ([#15](https://github.com/aunysillyme/website-build-skill/issues/15)).
+
+### Changed
+
+- TEAM consistently describes installing seven workers' files, opening each session yourself and carrying handoffs, with Researcher first; presentation checks guard that wording ([#17](https://github.com/aunysillyme/website-build-skill/issues/17)).
+
+### Fixed
+
+- Receipts under a symlinked parent such as macOS `/tmp` are accepted; found during the 2026-09-24 host trials for [#15](https://github.com/aunysillyme/website-build-skill/issues/15).
+
 ## [0.1.4] - 2026-09-23
 
 ### Added

package/CLAUDE.md

@@ -13,4 +13,5 @@ node --test test/*.test.mjs
 ```
 
 The installer is real; the native worker generator is not. Do not imply seven workers start.
-Native loading, account tools and independent-review access are UNVERIFIED until a real trial.
+Native SOLO loading is tested on Claude Code, Codex and the Grok Build CLI (one run each, receipts in docs/evidence/).
+Other hosts, TEAM, account tools and independent-review access are UNVERIFIED until a real trial.

package/CONTRIBUTING.md

@@ -24,8 +24,10 @@ Use synthetic fixtures and reserved example domains. Never paste real project tr
 ## Run locally
 
 Prerequisite: Node 18 or newer; no dependency install is required. The check matrix
-covers Node 18, 20, 22.22.3 and 24. The file installer is implemented; native worker
-generation and client activation remain UNVERIFIED. Registry publication is a separate
+covers Node 18, 20, 22.22.3 and 24 on Ubuntu, plus packed installs on macOS and Windows
+with Node 22.22.3. The file installer is implemented; live host
+session loading remains UNVERIFIED. TEAM installs files; you open each session yourself
+and carry the handoffs, with Researcher first. Registry publication is a separate
 release step, not something inferred from a working local executable.
 
 ```sh
@@ -35,7 +37,9 @@ node --test test/*.test.mjs
 ```
 
 Build rewrites only the five bundles and the index. Check is read-only and fails on drift.
-Tests use synthetic temporary directories inside this checkout and remove them afterward.
+Tests use synthetic temporary directories inside this checkout or the OS temporary
+directory and remove them afterward. Live host behaviour is verified by receipts, not
+by `npm test`; follow the [manual host gate](docs/evaluation/host-gate.md) for each skip.
 For a new check, demonstrate a failing fixture and a valid control. See [evaluation](docs/EVALUATION.md).
 The Markdown gate checks file targets, reference links, images, HTML links and heading anchors.
 External URLs require a separate live review; offline success does not prove availability.

package/README.md

@@ -91,13 +91,13 @@ Every site follows the same twelve stages, so your AI researches before it desig
 | Choice | What happens | Works with |
 |---|---|---|
 | **1 · Teach my AI** (SOLO) | One AI learns the whole method and does every job itself. Nothing else to install. | Any AI: Claude, ChatGPT, Grok, Cursor, Copilot |
-| **2 · Give me the team** (TEAM) | Seven specialist agents, one per job, starting with a researcher that gets them all current. One command installs their files; you open each session yourself. | Claude Code, Codex, Hermes, Antigravity, Grok Bot |
+| **2 · Give me the team** (TEAM) | Seven specialist agents, one per job. One command installs their files; you open each session yourself and carry the handoffs between them. Researcher goes first. | Claude Code, Codex, Hermes, Antigravity, Grok Bot |
 
 Not sure? Pick 1. Moving to 2 later keeps everything you have already done.
 
 The installer also asks where to save the work: an Obsidian vault folder, a folder on this computer (default: your project folder), Notion (a local working copy plus an export of the finished library), or another local folder. That folder becomes the workspace root.
 
-SOLO follows the same jobs with saved self-handoffs. TEAM gives each job a separate route:
+SOLO follows the same jobs with saved self-handoffs. TEAM uses seven sessions you open yourself, with handoffs you carry between them and Researcher first:
 
 - **Researcher:** saves the shared library before the other roles work.
 - **Coordinator:** accepts evidence, owns the brief and routes each handoff.
@@ -123,8 +123,8 @@ With any of these missing, the AI hands you the exact next step (a query plan, f
 
 ## Choose your host
 
-Each guide below has a documented setup with its own loading check; native loading on every
-host is awaiting a real-client trial, and [compatibility](docs/COMPATIBILITY.md) tracks
+Each guide below has a documented setup with its own loading check. Native loading is tested
+on Claude Code, Codex and the Grok Build CLI with dated receipts (one run each, limitations listed), and [compatibility](docs/COMPATIBILITY.md) tracks
 current status host by host.
 
 | Host | Set it up | What you get |
@@ -185,11 +185,11 @@ The [installer contract](docs/INSTALLER.md) defines preflight checks, exit codes
 
 **How do I teach Claude Code or Codex to build better websites?** Run `npx website-build-skill`, pick your host and let it copy the skill pack into your host's folder, then ask your AI to read the installed `SKILL.md`. It learns current practice in research, design, code, accessibility, performance, search and security before it touches your site.
 
-**Which AI tools does it work with?** Any AI that can read files works with the SOLO method, including Claude, ChatGPT, Grok, Cursor and Copilot. TEAM adds native routes for Claude Code, Codex, Hermes, Antigravity and Grok Bot; see [Choose your host](#choose-your-host) for each setup guide.
+**Which AI tools does it work with?** Any AI that can read files works with the SOLO method, including Claude, ChatGPT, Grok, Cursor and Copilot. TEAM installs the seven workers' files for Claude Code, Codex, Hermes, Antigravity and Grok Bot in one command; you open each session yourself and carry the handoffs between them, with Researcher first; see [Choose your host](#choose-your-host) for each setup guide.
 
 **What does my AI research before it builds?** It researches fourteen domains current to the day of your request, from design and accessibility to performance, security, stack and search, and saves a library with source URLs and access dates so later pages can refresh stale claims. See [What your AI learns](#what-your-ai-learns) for the full list.
 
-**Can one AI run it, or does it need a team?** Either. SOLO has one AI learn the whole method and do every job itself with nothing else to install; TEAM gives each of the seven jobs its own session, starting with a researcher that gets them all current. Pick SOLO if you are not sure; moving to TEAM later keeps everything you have already done.
+**Can one AI run it, or does it need a team?** Either. SOLO has one AI learn the whole method and do every job itself with nothing else to install; TEAM installs the seven workers' files in one command; you open each session yourself and carry the handoffs between them. Researcher goes first. Pick SOLO if you are not sure; moving to TEAM later keeps everything you have already done.
 
 **How do I remove it?** Run `npx website-build-skill --uninstall --target <your target> --dir . --yes`, using the target and directory from your install; it removes only the files the installer wrote that still match its receipt. See the [installer guide](docs/INSTALLER.md) for flags and exit codes.
 

package/adapters/agents-md.md

@@ -1,5 +1,7 @@
 # Generic agent router
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 SOLO: give a file-reading agent the root [AGENTS.md](../AGENTS.md) in this repository.
 For another project, copy the canonical folder intact into a new `.website-build-skill/` and merge this pointer into existing instructions:
 

package/adapters/antigravity.md

@@ -1,39 +1,23 @@
 # Antigravity
 
-Check the installed client schema, paths, orchestration and permissions before using native roles.
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
+Check the installed client's file access and session permissions before starting.
 Manual SOLO: copy the canonical folder into `.website-build-skill/` and explicitly ask the session to read its SKILL.md.
 Install the files: `npx website-build-skill --team --target antigravity --dir . --scope project --yes`.
 
-## Planned definition contract
-
-One complete canonical body per file at `.agents/agents/website-<role>.md`.
-Never automatically fall back to the user-level candidate `~/.gemini/config/agents/`.
-
-```yaml
----
-name: <agent_name>
-description: "<one line: what it does, when to use it, its permission boundaries>"
-subagent: true
-mainAgent: false
-model: inherit
-commandExecutionPolicy: "off"
-tools:
-  - <tool name>
-  - <tool name>
----
-
-# Agent System Instructions
-<the complete canonical role body>
-```
+## Open the workers
 
-Resolve method references to `.website-build-skill/`; retain project-relative artifact paths.
-Quote the policy string and round-trip all role text. Verify the declared policy with a permission probe.
-Keep Coordinator dormant while the parent coordinates. `mainAgent: true` and worker creation need separate verification.
-If the installed client exposes it, inspect with: `/agents`; then route the first assignment to Website Researcher.
+Open seven sessions yourself, Researcher first. In each session, load the complete
+`roles/<role>.md` from `.website-build-skill/`, plus the linked resources and current handoff.
+Use the [manual relay](grok.md#manual-fallback) to carry packets and attachments.
+Record each session reference, actual model family and available tools.
+Keep command execution off by default; verify the host setting with a permission probe.
+Give Reviewer a read-only session or candidate packet and return findings to Coordinator.
 
 ## Candidate tool mapping
 
-Use the supplied format as a design input and check it against the installed client.
+Use this checklist to inspect each session; tool names below remain candidates until observed.
 Use only tools the installed client exposes. Check image viewing and code execution separately from text reading and file writing.
 
 | Role | Declared observed tools| Reason and permission scope | Capability without an observed name; section 5.7 route |
@@ -48,10 +32,10 @@ Use only tools the installed client exposes. Check image viewing and code execut
 
 ## Settling checks
 
-- Parse and discover every role; record exact client version and expanded candidate path.
+- Open each complete role file; record exact client version and the path each session read.
 - Probe excluded Reviewer writes and execution through every inherited route; unchanged bytes are required.
 - Probe image inspection, generation, browser, build and source retrieval separately.
-- Verify parent routing, concurrency limits and research-first handoffs without duplicate Coordinators.
+- Verify each manually delivered handoff, concurrency limits and the research gate before Coordinator works.
 - Preserve source bytes and return a path-by-path receipt. Missing capability produces BLOCKED work.
 - References: [subagents](https://antigravity.google/docs/subagents), [agent manager](https://antigravity.google/docs/cli/commands/agents).
 

package/adapters/chatgpt-project.md

@@ -1,5 +1,7 @@
 # ChatGPT Project
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 Use an eligible account's Project instructions and file controls.
 Paste the instruction block below into project settings and attach the five bundles.
 This selects SOLO. Configure the Project through its account controls before starting.
@@ -23,7 +25,7 @@ Keep one primary action and truthful content consistent across every route.
 Never describe a proposed file, test, memory write, or deployment as completed.
 For each tool the next stage needs, use it or return the exact handoff for a capable runner.
 Follow the human's recorded install choice; this upload selects SOLO.
-A later switch to TEAM uses the chosen host's setup and verified separate workers.
+A later switch to TEAM installs the seven workers' files in one command; you open each session yourself and carry the handoffs between them, with Researcher first.
 Read all seven complete role bodies in team.md on either path. Before each job, complete
 its learning and dated research; save and reopen handoffs, including self-handoffs.
 Name the previous framing you are clearing when changing solo jobs.

package/adapters/claude-code.md

@@ -1,5 +1,7 @@
 # Claude Code
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 - Manual SOLO: copy the intact canonical folder into a new project `.claude/skills/website-build-skill/` directory. Preserve conflicts.
 - After checking native discovery, try `/website-build-skill`; for explicit loading, ask it to read its SKILL.md.
 - Plugin: the repository root contains metadata and discovers the canonical `skills/` tree. The plugin loads the method files.
@@ -8,14 +10,13 @@
 - Plugin setup: `claude plugin install website-build-skill@website-build-skill`.
 - Check the plugin invocation: `/website-build-skill:website-build-skill`.
 - Install the files: `npx website-build-skill --team --target claude-code --dir . --scope project --yes`.
-- TEAM fallback: create separate sessions with complete [role bodies](../docs/bundles/team.md), Researcher first. Use the [manual relay](grok.md#manual-fallback).
-- Planned native definitions: `.claude/agents/website-<role>.md`, YAML name and description plus the complete canonical body, with references resolved to the installed core.
+- TEAM setup: open separate sessions with complete [role bodies](../docs/bundles/team.md), Researcher first. Use the [manual relay](grok.md#manual-fallback).
 - Source targets: [skills](https://code.claude.com/docs/en/skills) and [subagents](https://code.claude.com/docs/en/sub-agents).
 
 
 ## Check that it loaded
 
-Native loading on this host is awaiting a real-client trial; the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).
+Native loading was tested on Claude Code 2.1.281 (macOS, SOLO, 2026-09-24; one run, limitations in the [receipt](../docs/evidence/host-trial-claude-code-2026-09-24.json)); the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).
 
 Give the host a synthetic brief and ask it to identify the entrypoint and complete asset list.
 Record client version, date, exact path, tool availability and the observed invocation.

package/adapters/claude-desktop.md

@@ -1,5 +1,7 @@
 # Claude Desktop
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 Check the upload controls and menu labels in your account.
 Available manual route: attach the five bundles and paste the [shared instructions](chatgpt-project.md#instruction-block).
 For skill ZIP upload, prepare an archive with one complete `website-build-skill/` directory, including its manifest and relative resources.

package/adapters/codex.md

@@ -1,17 +1,18 @@
 # Codex
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 - Manual SOLO: copy the full canonical folder to a new `.agents/skills/website-build-skill/` in the chosen project.
 - Load the skill: ask the host to load `website-build-skill`; confirm the exact file it opens.
 - Install the files: `npx website-build-skill --team --target codex --dir . --scope project --yes`.
-- Planned native definitions: `.codex/agents/website-<role>.toml` with name, description and full canonical developer_instructions. Round-trip quotes and backslashes.
-- Fallback: separate sessions using [the full team bundle](../docs/bundles/team.md). Do not overwrite `.codex/config.toml` or infer independence from two model names.
+- TEAM sessions use [the full team bundle](../docs/bundles/team.md). Do not overwrite `.codex/config.toml` or infer independence from two model names.
 - Shared core: Hermes may use the same candidate path; preserve identical content and retain the core until every owner releases it.
 - Sources to verify: [skills](https://learn.chatgpt.com/docs/build-skills), [custom agents](https://learn.chatgpt.com/docs/agent-configuration/subagents).
 
 
 ## Check that it loaded
 
-Native loading on this host is awaiting a real-client trial; the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).
+Native loading was tested on Codex CLI 0.154.0 (macOS, SOLO, 2026-09-24; one run, limitations in the [receipt](../docs/evidence/host-trial-codex-2026-09-24.json)); the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).
 
 Give the host a synthetic brief and ask it to identify the entrypoint and complete asset list.
 Record client version, date, exact path, tool availability and the observed invocation.

package/adapters/custom-gpt.md

@@ -1,5 +1,7 @@
 # Custom GPT
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 In an eligible account, put the block below in Instructions and the bundles in Knowledge.
 Enable only available, authorized research/file tools. Use Preview to exercise a synthetic brief through research and mockups.
 Save and reattach a state packet in each new chat.
@@ -23,7 +25,7 @@ Keep one primary action and truthful content consistent across every route.
 Never describe a proposed file, test, memory write, or deployment as completed.
 For each tool the next stage needs, use it or return the exact handoff for a capable runner.
 Follow the human's recorded install choice; this upload selects SOLO.
-A later switch to TEAM uses the chosen host's setup and verified separate workers.
+A later switch to TEAM installs the seven workers' files in one command; you open each session yourself and carry the handoffs between them, with Researcher first.
 Read all seven complete role bodies in team.md on either path. Before each job, complete
 its learning and dated research; save and reopen handoffs, including self-handoffs.
 Name the previous framing you are clearing when changing solo jobs.

package/adapters/grok.md

@@ -1,20 +1,24 @@
 # Grok
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 Set up Bots through the account controls using the complete roles and manual relay below.
 See [compatibility](../docs/COMPATIBILITY.md) for setup evidence and host trials.
 
 - SOLO: paste the starter in [zero-install](zero-install.md), or give a file-capable session the complete canonical skill.
-- TEAM: attach all five [bundles](../docs/bundles/team.md), then paste the setup request below.
-- Native skill candidate: `.grok/skills/website-build-skill/`; discovery and invocation require a clean-client check. Native loading on this host is awaiting a real-client trial; the check above confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).
+- TEAM: install or attach all five [bundles](../docs/bundles/team.md), open the seven sessions yourself, then paste the setup request below in each session.
+- Native skill (Grok Build CLI): install with `--target grok`, which writes `.grok/skills/website-build-skill/`, then trust the project folder (accept the trust prompt, or run `grok --trust` there once). Grok Build offers project skills only in a trusted folder. Native loading was tested on Grok Build CLI 1.0.40 (macOS, SOLO, trusted folder, 2026-09-24; one run, limitations in the [receipt](../docs/evidence/host-trial-grok-build-2026-09-24.json)); `grok inspect --json` lists the skill with source `project` when it is available to you. Grok Bot (the Bots app) is awaiting its own trial. Current status: [compatibility](../docs/COMPATIBILITY.md).
 - Independence: workers from one model family leave the independent release gate BLOCKED.
 - Reference: [Bot setup](https://docs.x.ai/grok-bot/bots), [collaboration](https://docs.x.ai/grok-bot/chat-and-collaboration), [skills](https://docs.x.ai/build/features/skills-plugins-marketplaces). Use these references when checking the installed controls.
 
 ```text
-Give me the team (option 2). Use the attached team.md and create Website Researcher first, then Website Coordinator, Website Designer, Website Graphics, Website Builder, Website Optimizer, and Website Reviewer with their complete role bodies. Use only controls actually available in this account. Return seven setup acknowledgements with routes, model families and tool limits. If Bot creation is unavailable, show the manual fallback. Give my request to Researcher first; every other worker waits for the saved-library gate. Use a reviewer from a different model family for independent review.
+Give me the team (option 2). I open each session myself and carry the handoffs between them, with Researcher first. Use the attached team.md and the complete role body for this session. Return its setup acknowledgement with session reference, model family and tool limits. I collect seven acknowledgements through the manual setup below. Give my request to Researcher first; every other worker waits for the saved-library gate. Use a reviewer from a different model family for independent review.
 ```
 
 ## 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.
@@ -37,7 +41,7 @@ Give me the team (option 2). Use the attached team.md and create Website Researc
 **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.
 
@@ -69,7 +73,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**
@@ -90,11 +94,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.

package/adapters/hermes.md

@@ -1,5 +1,7 @@
 # Hermes
 
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+
 Check project trust and the installed client's loading controls before starting.
 Manual SOLO: copy the complete canonical folder into a new `.agents/skills/website-build-skill/` in the chosen project.
 For explicit loading, ask the session to read its SKILL.md directly.
@@ -9,30 +11,26 @@ Do not create version-control state or alter global settings during a copy.
 Install the files: `npx website-build-skill --team --target hermes --dir . --scope project --yes --bundle-dir team-aliases`.
 The path is relative to the installed skill folder, so the alias files land in `.agents/skills/website-build-skill/team-aliases/` and the path must stay inside that folder.
 
-## Two planned branches
-
-| Branch | Required evidence | Output contract |
-| --- | --- | --- |
-| A: declarative roles | Current schema, exact path, native discovery and permissions | Seven full canonical bodies in verified native files |
-| B: separate sessions | Real session routes and artifact read-back | Core plus `.website-build-skill/team/hermes/setup.md`, seven session packets and an explicit alias destination |
+## Open the workers
 
-Select a native branch only after collecting its required evidence. The installer must fail closed on an unknown native schema.
-Session packets include each full role, tools, family, ownership, accessible library revision and handoff contract.
-An alias loads instructions. Verify each worker through its actual session route.
-Manual fallback: use separate chats and [the team relay](grok.md#manual-fallback).
-Check that each worker can read the assigned revision, including any uncommitted files it needs.
-Check Reviewer permissions on inherited tools; use a read-only packet and returned findings when needed.
+Open seven separate sessions yourself, Researcher first. Supply each complete role body
+from `.agents/skills/website-build-skill/roles/`, the linked resources and its current handoff.
+The `team-aliases` directory holds copies of the five bundles. An alias loads instructions;
+verify each worker through its own session reference and carry the handoffs yourself.
+Use [the team relay](grok.md#manual-fallback) and check each worker can read the assigned
+revision, including any uncommitted files it needs. Check Reviewer permissions on inherited
+tools; use a read-only packet and returned findings when needed.
 
 ## Shared core and receipt
 
 Codex and Hermes candidate paths overlap. Compare content before writing and preserve conflicts.
 Test installation in both orders, partial receipts and reference ownership before supporting shared uninstall.
 An explicit bundle directory authorizes only that destination. Never write a home-directory alias implicitly.
-The receipt enumerates core files, setup packets, alias, hashes, mode and pending activation.
+The receipt enumerates core files, bundles, alias copies, hashes, mode and pending integration.
 
 ## Settling checks
 
-Verify project trust before/after explicit authorization, native preload, all manifest assets and both session routes.
+Verify project trust before/after explicit authorization, native preload, all manifest assets and each session reference.
 Verify seven acknowledgements, source-preserving relay, no downstream work before research and denied Reviewer writes.
 Probe image, browser, execution and independent-family access separately.
 Source targets: [skills](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills), [delegation](https://hermes-agent.nousresearch.com/docs/user-guide/features/delegation), [CLI](https://hermes-agent.nousresearch.com/docs/user-guide/cli).

package/adapters/team.yaml

@@ -1,3 +1,5 @@
+# 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/COMPATIBILITY.md

@@ -2,7 +2,18 @@
 
 ## Tested hosts
 
-No host below has a completed real-client trial yet. Each host has a documented setup and
+Three hosts have a dated native-loading receipt. Each covers SOLO skill discovery and loading
+on the exact version below, from one run under the operator's existing client configuration
+(each receipt lists its limitations); the full SOLO build route, TEAM and deployment stay
+documented until a trial records them.
+
+| Host | Version and system | Mode and scope | Date | Receipt |
+|---|---|---|---|---|
+| Claude Code | 2.1.281, macOS 26.6.2 arm64 | SOLO, native loading tested | 2026-09-24 | [receipt](evidence/host-trial-claude-code-2026-09-24.json) |
+| Codex CLI | 0.154.0, macOS 26.6.2 arm64 | SOLO, native loading tested | 2026-09-24 | [receipt](evidence/host-trial-codex-2026-09-24.json) |
+| Grok Build CLI | 1.0.40, macOS 26.6.2 arm64 | SOLO, native loading tested in a trusted folder | 2026-09-24 | [receipt](evidence/host-trial-grok-build-2026-09-24.json) |
+
+Every other host has a documented setup and
 a check you run, in its own adapter guide, to confirm it loaded on yours. A host moves from
 documented to tested when its receipt records the client/runtime version, trial date,
 operating system, package revision, installed paths and hashes, invocation, observed
@@ -30,7 +41,7 @@ when its receipt demonstrates loading, file access, tool permissions and the sel
 
 - **Documentation:** save the opened official source, version, access date and setup facts it supports.
 - **Native loading:** record the actual entrypoint and every resource the client can read.
-- **TEAM:** record separate routes, setup acknowledgements, model families and permission probes.
+- **TEAM:** one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first. Record separate session references, setup acknowledgements, model families and permission probes.
 - **Delivery:** record fresh package installs for each operating system being claimed, including Linux and Windows.
 - **Uploads and URLs:** verify account ZIP controls and raw-URL retrieval in the actual client.
 - **Runtime:** the package declares Node 18 or newer; [the check workflow](https://github.com/aunysillyme/website-build-skill/blob/main/.github/workflows/check.yml) defines its runtime matrix.

package/docs/INSTALLER.md

@@ -3,7 +3,7 @@
 `npx website-build-skill` copies the canonical files, verifies them by read-back and writes a
 receipt of exactly what it wrote. Open the chosen host and ask it to read the installed entrypoint.
 See [compatibility](COMPATIBILITY.md) for host setup evidence and loading checks.
-For TEAM, use the complete role bundles with separate sessions and manual handoffs.
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
 
 ## Manual copy
 
@@ -57,12 +57,15 @@ Append `#<reviewed-commit-sha>` to the repository reference for a reproducible i
 - Read-back: every file is re-read from disk and digested after the write pass. A digest taken from the bytes the installer meant to write is a record of the intention, not of what is on disk, and the receipt only ever carries the second one.
 - Ownership across runs: a reinstall that writes fewer files keeps owning what an earlier run wrote, so a SOLO install over a TEAM install does not orphan the bundles.
 
-## Native team branches
+## TEAM sessions and handoffs
 
-Generate complete canonical bodies, never independent role summaries.
-Antigravity uses per-role Markdown only after schema, path and permission tests.
-Hermes branch A requires verified declarative role support. Branch B uses separate-session packets and an explicitly scoped skill alias; alias loading never proves worker creation.
-Both branches keep Researcher first, seven acknowledgements, a blocked downstream gate and a different-family Reviewer.
+The command copies the complete role files and five bundles. Open each worker's session
+yourself and supply its complete role body, readable resources and current handoff.
+Start Researcher first; carry its passing receipt and library to Coordinator before
+passing assignments to later workers. Record seven setup acknowledgements and use a
+different-family Reviewer. Enforce read-only review through host controls or a read-only packet.
+The Hermes alias copies bundles into the explicitly selected directory inside the skill folder.
+Session references and permissions require your own checks in the chosen host.
 See [Antigravity](../adapters/antigravity.md), [Hermes](../adapters/hermes.md) and [team ownership](../adapters/team.yaml).
 
 ## Verify the installation

package/docs/METHOD.md

@@ -24,7 +24,8 @@ A derived floor is a qualified lower bound, never proof of the actual day or lat
 Missing provenance or current research keeps dependent work BLOCKED.
 
 SOLO follows all seven roles sequentially with self-handoffs and a framing reset.
-TEAM needs separate routes and acknowledgements, one writer per artifact, and a saved research gate.
+TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.
+Record seven setup acknowledgements, one writer per artifact, and a saved research gate.
 Neither mode earns independent review from a second name in the same model family.
 Use PASS, FAIL, BLOCKED or NOT APPLICABLE with evidence. Never convert absence into a pass.
 

package/docs/README.md

@@ -10,6 +10,7 @@ Start with the guide for the job you want to do:
 | [Tips](TIPS.md) | Brand, design, scope and research practices |
 | [Provenance](PROVENANCE.md) | Sources, attribution and the canonical file map |
 | [Evaluation](EVALUATION.md) | Repository checks and adversarial test cases |
+| [Manual host gate](evaluation/host-gate.md) | Live-host skips, per-OS loading and ZIP trials, with required receipts |
 | [Library check](LIBRARY-CHECK.md) | Validate saved research claims and source receipts |
 | [Bundles](#bundles) | The full method as files to attach or paste into a chat |
 

package/docs/bundles/method.md

@@ -69,7 +69,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.
@@ -121,7 +122,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](../../skills/website-build-skill/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.