website-build-skill 0.1.0

package/adapters/zero-install.md

@@ -0,0 +1,17 @@
+# Zero install
+
+Paste this self-contained starter into an AI chat. It needs no repository retrieval, clone or npm.
+It establishes the first task; attach the full bundles for the complete method.
+
+```text
+Use option 1: Teach my AI. Help me build a website with Research, Learn, Ingest, Scope, Match, Mock, Choose, Build, Prove, Protect, Challenge and Ship. First act as Researcher: establish the request date from host evidence, then research the site's design, accessibility, performance, security, stack and search needs using current opened sources. Save a library with source URLs, publication dates or unknown, access dates, disagreements and checklists. If you lack search, say research is BLOCKED and return a query plan. If you lack files, return named bodies for me to save and reattach before passing the save gate. Only then confirm my brief, extract my brand or request profile/banner screenshots, and show three visual mockups. Wait for my named selection before site code. Choose the smallest fitting stack. Keep evidence and handoffs between roles. Protect means security headers and the ship security checklist; Challenge means a different model family reviews a fixed candidate read-only, and I authorize release. This starter is a compact entrypoint, so do not claim Ship until the five bundles or the skill folder supply the full twelve-stage route and its checklists. Start with the site request I provide next; ask only for missing inputs that change the work.
+```
+
+## Full method
+
+Paste or attach [method](../docs/bundles/method.md), [prompts](../docs/bundles/prompts.md), [playbooks](../docs/bundles/playbooks.md), [checklists](../docs/bundles/checklists.md) and [team](../docs/bundles/team.md).
+They exist locally and in the public repository: browse [the bundle folder](https://github.com/aunysillyme/website-build-skill/tree/main/docs/bundles), download [the main archive](https://github.com/aunysillyme/website-build-skill/archive/refs/heads/main.zip), or open a raw file such as
+`https://raw.githubusercontent.com/aunysillyme/website-build-skill/main/docs/bundles/method.md`.
+Retrieval serves the files; a host bootstrapping itself from a URL is UNVERIFIED.
+Never substitute a similar repository when retrieval fails. Pin one revision and verify manifest hashes before combining files.
+Without retrieval, supply the text itself. A URL alone is not loaded knowledge.

package/bin/website-build-skill.mjs

@@ -0,0 +1,6 @@
+#!/usr/bin/env node
+import { main } from '../src/cli.mjs';
+
+const { code, message } = await main();
+(code === 2 || code === 3 || code === 4 ? process.stderr : process.stdout).write(`${message}\n`);
+process.exitCode = code;

package/docs/COMPATIBILITY.md

@@ -0,0 +1,34 @@
+# Compatibility
+
+Status vocabulary: DOCUMENTED requires opened official evidence; TESTED requires a recorded actual trial.
+This repository currently makes no TESTED host claim. All package integrations below are UNVERIFIED.
+Candidate interfaces come from the design specification; consult the linked official source before a live trial.
+
+| Host | Manual payload | What to verify | Source |
+| --- | --- | --- | --- |
+| Claude Code | Complete skill or root plugin | Discovery, invocation, assets and worker isolation | [skills](https://code.claude.com/docs/en/skills) |
+| Codex | Complete skill, explicit router | Shared destination, role configuration, real family | [skills](https://learn.chatgpt.com/docs/build-skills) |
+| Hermes | Complete skill, separate sessions | Trust, alias semantics, routes, inherited permissions | [skills](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills) |
+| Antigravity | Explicit core pointer | Schema, paths, quoted off, routing, denied writes | [subagents](https://antigravity.google/docs/subagents) |
+| Grok Bot | Five bundles, manual roles | Actual account controls, routes, image relay | [Bots](https://docs.x.ai/grok-bot/bots) |
+| Claude Desktop | Five bundles; future skill ZIP | Account upload controls and loaded resources | [skills](https://support.claude.com/en/articles/12512180-use-skills-in-claude) |
+| ChatGPT Project/custom GPT | Instructions plus five bundles | File access, tool availability, state reattachment | [Projects](https://help.openai.com/en/articles/10169521-projects-in-chatgpt) |
+| Generic file-reading agent | Explicit core pointer | Router read-back and preserved instructions | [adapter](../adapters/agents-md.md) |
+
+## Evidence required per row
+
+Record exact client/runtime version, actual trial date, operating system, artifact revision,
+installed file list and hashes, invocation, observed outputs, negative cases and limitations.
+Retain a sanitized receipt in this repository before promoting the claim.
+Documentation alone cannot establish native loading, enforcement or automatic worker creation.
+Hosted repository checks have a [revision-bound baseline receipt](evidence/audit-baseline.json).
+Those Linux CI checks do not establish client activation. Windows/client trials, registry
+delivery, ZIP upload and raw-URL bootstrap remain UNVERIFIED.
+The maintainer runtime is Node 22.22.3. The package declares Node 18 or newer, and the check
+matrix runs 18, 20, 22.22.3 and 24; no other runtime is claimed.
+
+## Degradation
+
+The [canonical missing-capability table](../skills/website-build-skill/playbooks/research-and-memory.md#missing-capability-table)
+is included in method and team bundles. It keeps research, visual mockups, measurements,
+independent review and release blocked when their required tools or evidence are missing.

package/docs/EVALUATION.md

@@ -0,0 +1,109 @@
+# Evaluation and evidence
+
+Local deterministic checks and live agent behavior are different claims.
+The checks below reject repository defects; they cannot prove a host obeys an instruction.
+The [baseline receipt](evidence/audit-baseline.json) records a hosted CI run for one
+exact revision. Platform activation, package publication and live model behavior
+remain unproved by that run; check the current candidate separately.
+
+## Run the repository gates
+
+```sh
+node scripts/check.mjs
+node --test test/*.test.mjs
+```
+
+Check performs no writes. The test suite copies synthetic fixtures into `.test-work/`,
+mutates one condition, asserts the named rejection and removes each scratch copy.
+The GREEN control and the RED cases run against the same policy the CLI and CI use; there is
+no separate test-only exemption. The public-identifier policy is resolved: the owning account
+is permitted on the exact CODEOWNERS line and inside repository URLs, and the supported host's
+product name is permitted as a product name. A path-shaped use of that product name is still
+rejected, so a local working directory cannot pass through the exemption, and a test covers
+that case. Private identifiers are also rejected in filenames, not only in file contents.
+
+| RED case | Named rejection | Regression |
+| --- | --- | --- |
+| Private machine path | PRIVACY | RED01 in privacy.test.mjs |
+| Private issue URL or identifier | PRIVACY | RED02 in privacy.test.mjs |
+| Unavailable install advertised without a same-line label | INSTALL_CLAIM | RED03 in content.test.mjs |
+| Missing Markdown relative target | LINK | RED04 plus image/reference/HTML/anchor controls |
+| Generated bundle bytes drift | BUNDLE_DRIFT | RED05 in content.test.mjs |
+| Floating action reference | ACTION_PIN | RED06 plus reusable-action control |
+| Write token on a read-only job | WORKFLOW_PERMISSIONS | RED07 plus top-level/all-write controls |
+| Inactive archive enters active prompts | ARCHIVE_EXCLUSION | RED08 plus manifest route checks |
+| Unsupported test, measurement, publication or compatibility claim | CLAIM_EVIDENCE | RED09 in README, new docs and CHANGELOG |
+
+## Editorial claim gate
+
+Every public Markdown document outside canonical assets, generated bundles and inactive test fixtures
+has a reviewed checksum in [content-review.json](evidence/content-review.json).
+New or changed prose fails closed until a maintainer reviews it. This is intentionally broader than a keyword search.
+The generator never updates that ledger. Canonical claims remain covered by manifest hashes and source review;
+generated text must exactly match those sources. A checksum binds review scope, not factual truth.
+The current disposition permits instructions and explicitly qualified status only.
+A positive claim instead needs its exact text and a JSON evidence receipt under `docs/evidence/`
+with command, environment, date, exitCode, artifactSha256 and observed result.
+Reviewers must read that receipt and reproduce material results; a structurally valid receipt can still be false.
+A change to the ledger itself requires code-owner review. No content checker can replace that authority.
+
+## Privacy scope
+
+The gate scans every public file, including hidden community metadata, fixtures and generated bundles.
+It rejects personal paths, private identifiers, personal names and email addresses without echoing their values.
+Production exceptions are exact license authorship and repository URL namespaces.
+The supported public product name and exact CODEOWNERS handle are narrow, resolved
+exceptions implemented by privacyIssues. Path-shaped uses remain rejected. These
+exceptions do not permit personal identifiers elsewhere.
+The unchanged inactive archive is checksum-pinned; its historical path is never copied into active prompts.
+Scratch fixture copies and version-control internals are outside the public-tree walker.
+The final raw recursive sweep is a separate report step, so any literal policy conflict stays visible.
+
+## Structural checks
+
+Manifest assets must exist, match digests and contain all seven populated role bodies.
+The README question must match the canonical template. Every generated bundle uses manifest order.
+The workflow validator accepts the JSON subset of YAML, checks every action reference recursively,
+requires read-only permissions except the release publish job's scoped OIDC token, disables persisted checkout credentials,
+and requires concurrency cancellation and job timeouts. Other YAML syntax fails closed pending parser review.
+External URL reachability is outside the offline link check.
+
+## Planned live behavior evaluation
+
+Run the [end-to-end host trial](evaluation/host-trial.md) to collect a complete
+synthetic SOLO local-preview result and the negative cases below. Its receipt template
+is deliberately NOT RUN. The method's outcome remains unproved until actual artifacts
+and a reproducible trial are reviewed; adding the protocol does not establish support.
+
+| Scenario | Required observation |
+| --- | --- |
+| Missing brand kit | Requests suitable screenshots and labels inferences |
+| No search or stale library | Returns queries/unresolved claims; no downstream design |
+| Missing source or date | Blocks research and dependent roles |
+| SOLO transition | Reopens library, completes learning and saves self-handoff |
+| TEAM transition | Seven actual routes; Researcher first; Coordinator reads saved evidence |
+| Same-family Reviewer | INTERNAL critique, independent gate BLOCKED |
+| No memory | Returns a save/reattach packet without claiming persistence |
+| Conflicting accents | Surfaces conflict and requests only the decision that changes the design |
+| Hostile fetched text | Refuses instruction injection and keeps authorized write scope |
+| Reviewer allegation | Reproduces before recording a confirmed defect |
+| Date ladder and reuse | Rejects every inactive ASK DATE fixture and passes genuine evidence controls |
+
+These are evaluation specifications, not completed trials. Installer regressions run
+as ordinary tests. Cross-platform fresh-package and live-date evaluations remain TODO.
+Run live evaluations only with explicit tool access and an approved budget.
+
+## File and evidence index
+
+- [Historical local run](evidence/local-checks.json): an earlier TypeScript-era source snapshot; preserve it as historical evidence, not current-candidate validation.
+- [Audit baseline](evidence/audit-baseline.json): exact baseline revision, local checks, hosted CI and registry observation. Rerun gates after changes.
+
+- [Floor coverage register](evidence/floor.json): exhaustive section-4 filenames and implementation scope.
+- [Content regressions](https://github.com/aunysillyme/website-build-skill/blob/main/test/content.test.mjs), [privacy regressions](https://github.com/aunysillyme/website-build-skill/blob/main/test/privacy.test.mjs).
+- [Installer boundary](https://github.com/aunysillyme/website-build-skill/blob/main/test/installer.test.mjs), [package boundary](https://github.com/aunysillyme/website-build-skill/blob/main/test/package.test.mjs), [date routing](https://github.com/aunysillyme/website-build-skill/blob/main/test/research-date.test.mjs).
+- [Synthetic missing asset](https://github.com/aunysillyme/website-build-skill/blob/main/test/fixtures/invalid-manifest.json), [brand conflict](https://github.com/aunysillyme/website-build-skill/blob/main/test/fixtures/conflicting-brand.json).
+- [Malicious source](https://github.com/aunysillyme/website-build-skill/blob/main/test/fixtures/malicious-source.md), [incomplete handoff](https://github.com/aunysillyme/website-build-skill/blob/main/test/fixtures/incomplete-handoff.yaml), [date cases](https://github.com/aunysillyme/website-build-skill/blob/main/test/fixtures/ask-date-cases.md).
+- [Bundle generator](../src/bundle.mjs), [validator](../src/validate.mjs), [build entry](https://github.com/aunysillyme/website-build-skill/blob/main/scripts/build.mjs), [check entry](https://github.com/aunysillyme/website-build-skill/blob/main/scripts/check.mjs).
+- [CLI contract](../src/cli.mjs), [choice accessor](../src/choice.mjs), [destination catalog](../src/catalog.mjs), [install contract](../src/install.mjs), [agent contract](../src/agents.mjs).
+- [Entry point](../bin/website-build-skill.mjs), [install engine](../src/install.mjs), [package metadata](../package.json), [lock metadata](https://github.com/aunysillyme/website-build-skill/blob/main/package-lock.json).
+- [Check workflow](https://github.com/aunysillyme/website-build-skill/blob/main/.github/workflows/check.yml), [release boundary](https://github.com/aunysillyme/website-build-skill/blob/main/.github/workflows/release.yml).

package/docs/INSTALLER.md

@@ -0,0 +1,73 @@
+# Installer contract
+
+Status: the installer is implemented; native worker generation is not.
+`npx github:aunysillyme/website-build-skill` copies the canonical files, verifies them by read-back and writes a
+receipt of exactly what it wrote. It never creates a running agent, and host activation stays
+UNVERIFIED until a real client trial. The manual copy route below still works and needs no Node.
+
+## Manual copy available now
+
+Copy the complete `skills/website-build-skill/` directory into a new, empty destination:
+
+| Target | Project destination | Activation status |
+| --- | --- | --- |
+| Claude Code | `.claude/skills/website-build-skill/` | UNVERIFIED; read back the entrypoint and assets |
+| Codex | `.agents/skills/website-build-skill/` | UNVERIFIED; inspect discovery and invocation |
+| Hermes | `.agents/skills/website-build-skill/` | UNVERIFIED; trust and shared discovery need a trial |
+| Antigravity | `.website-build-skill/` | Explicit file-reading route; native definitions planned |
+| Generic agent | `.website-build-skill/` | Ask it to read the entrypoint; preserve existing routers |
+| Grok file-capable host | `.grok/skills/website-build-skill/` | UNVERIFIED; otherwise paste bundles |
+
+Do not merge into a conflicting directory. Compare and preserve existing files first.
+Copy a router pointer into existing project instructions only with authorization; do not replace them.
+A copied file is prepared content. Discovery and activation require a separate read-back.
+For chat-only hosts, attach the five bundles and use the [Project instructions](../adapters/chatgpt-project.md).
+
+## Command interface
+
+Before the package is on npm, the same entry point runs from the repository with
+`npx github:aunysillyme/website-build-skill <flags>`, verified to print its version.
+
+Installs the files, activation still UNVERIFIED: `npx github:aunysillyme/website-build-skill --solo --target codex --dir . --scope project --yes`.
+Installs the files, activation still UNVERIFIED: `npx github:aunysillyme/website-build-skill --team --target antigravity --dir . --scope project --yes`.
+
+- Choice: mutually exclusive `--solo` / `--team`; no arguments asks the canonical human question first.
+- Target: `claude-code`, `codex`, `hermes`, `antigravity`, `grok`, `agents`, `chatgpt`, `portable`.
+- Scope: project by default; user scope requires explicit selection, never implicit fallback.
+- Destination: `--dir` is explicit; `--bundle-dir` is accepted only for the Hermes team alias.
+- Output root: `--output-dir` selects an existing directory separately from the skill destination. Interactive setup collects the save-location choice and path; Enter on the local-folder path uses the website project directory. The receipt records `outputRoot` and optional `outputStorage` (kind and Notion export target). Researcher consumes those values before writing `<outputRoot>/site-work/research/library/scope.md`. The installer only probes the root; it does not create a library or export to Notion. Headless setup without `--output-dir` leaves the root unset for Researcher to ask before writing.
+- Notion: export destination only. Interactive setup requires both the existing local working directory (authoritative) and a page URL or name for later export. No credentials are requested and no network upload occurs.
+- Writability: confirm the output root by writing and reading back before any sweep; an unwritable root fails without partial writes.
+- Headless: `--yes` requires mode, target and destination; EOF and missing arguments fail without writes.
+- Preflight: validate the entire intended output set before writes; reject symlinks, traversal and conflicts.
+- Paths: the project root you name is canonicalized, so a symlinked ancestor such as macOS `/tmp` installs normally. Every segment at or below that root is refused when it is a symlink, because that is what a third party can plant in an install target.
+- Idempotence: identical bytes are a no-op; changed bytes produce a reviewable diff without overwriting.
+- Dry run: `--dry-run` makes no writes, including directories, receipts or aliases.
+- Runtime: offline after package retrieval; no telemetry, profiles, background tasks or lifecycle hooks.
+- Receipt: list every actual path and digest, mode, target, definition and unresolved activation check.
+- Integration: preserve existing routers and emit a named integration snippet; unmerged means activation pending.
+- Interruption: record truthful partial results; never advertise an all-or-nothing transaction without evidence.
+- Exit policy: 0 complete, 2 invalid input, 3 preflight conflict, 4 interrupted write, 5 activation pending. 5 is a completed install whose integration snippet is unmerged, not a failure.
+- Uninstall: receipt-based, removing only files this package actually wrote and whose bytes still match the receipt. A file that was already on disk before the install, and therefore recorded as identical, is kept: installing it was a no-op and removing it would be taking something that is not ours. A changed file is kept and named, and so is a file the receipt does not list. It removes empty directories it created INSIDE the destination; the destination directory itself and any parent directories it had to create are left in place, because the receipt cannot tell them apart from directories that were already there.
+- Destination: decided by `--target` and `--dir`, or by where the receipt sits when only `--receipt` is given. It is never read out of the receipt's own text, so an edited or planted receipt cannot point a removal somewhere else.
+- 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
+
+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.
+See [Antigravity](../adapters/antigravity.md), [Hermes](../adapters/hermes.md) and [team ownership](../adapters/team.yaml).
+
+## What is proven, and what is not
+
+Proven by the test suite and by hand on macOS: traversal and symlink refusal at and below the
+project root, whole-set conflict refusal, idempotent reruns, dry run writing nothing, an
+unwritable output root failing before any skill file, receipt digests matching the bytes on
+disk, uninstall keeping a changed file, router files left untouched with exit 5.
+
+Not proven by anyone: host discovery or activation on any client, a fresh tarball trial on
+Linux or Windows, and the native worker generation described below. Record actual results
+before changing a compatibility row.

package/docs/LIBRARY-CHECK.md

@@ -0,0 +1,95 @@
+# Library receipt checker
+
+## What and why
+
+`check-library` checks that a research ledger's opened claims have consistent local
+fetch receipts. It cannot prove a fetch happened, that an excerpt is verbatim, or
+that the excerpt supports the claim. Independent live-page review remains required.
+
+## Trigger
+
+Run before research acceptance and again when claims or receipts change. AD03,
+AD04 and AD07 consume the result; AD09 adds independent source re-fetching.
+
+## Invocation chain
+
+Run `website-build-skill check-library <site-work-dir>`. In a repository checkout,
+run `node bin/website-build-skill.mjs check-library <site-work-dir>`.
+The binary calls `src/cli.mjs`, which calls `checkLibrary` in `src/library-check.mjs`.
+The binary prints the result and sets its process exit code. Exit 0 means local
+receipt consistency; exit 2 means invalid input or a failed check, printed to stderr.
+
+## Dependencies
+
+Node and the package's own modules. No external packages, network access, fetch tool
+credentials, installation writes or background services are needed by the checker.
+
+## Reads
+
+Relative to the supplied site-work directory, read `research/library/sources.md`
+and `research/library/receipts/<CLAIM-ID>.md` for each ledger claim. Refuse symlink
+paths and unsafe claim IDs. Claim IDs begin with `CLAIM-` and continue with letters,
+digits, hyphens or underscores. Every table row has these columns:
+
+```text
+| Claim ID | Domain | Statement | URL | Published | Accessed | Status | Dependents |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+```
+
+Use plain cells, escape a literal pipe as `\|`, and write `unknown` for an absent
+publication date. Column names ignore case, spaces, hyphens and underscores.
+The status vocabulary is `OPENED` or `UNVERIFIED`; legacy `Verified` labels in any
+case receive the same receipt checks as `OPENED`, never an exemption.
+
+Each receipt contains plain `url:`, `fetched_at:`, `tool:`, `result:`, `published:`
+and `excerpt:` fields. Use an environment-supplied UTC timestamp ending in `Z`,
+with seconds and optional three-digit milliseconds. Copy the publication date
+verbatim into both ledger and receipt, or use `unknown`. The date must appear in
+the excerpt. Put the verbatim supporting passage after `excerpt: |`, with every
+line indented two spaces; a single-line `excerpt:` is also accepted. The trimmed
+passage must contain at least 80 characters. Preserve fetch evidence at fetch time.
+
+## Writes
+
+None. The caller captures the command, exit code and complete output in the gate
+record. The checker lists UNVERIFIED claims even on a successful consistency check.
+
+## The closed loop
+
+Nothing watches a project library automatically. Researcher runs the check and
+corrects findings; Coordinator reopens the artifacts and records acceptance.
+An acted-on UNVERIFIED claim keeps acceptance BLOCKED even when the checker exits 0.
+Reviewer independently re-fetches the AD09 sample and reports excerpt mismatches.
+Send checker defects to the package maintainer with a synthetic reproducer; send
+source discrepancies to Researcher by claim ID and pause dependent decisions.
+
+## Failure modes
+
+Missing or malformed ledgers, unsafe paths, duplicate claim IDs, absent or incomplete
+receipts, short excerpts, URL differences, inconsistent publication dates and
+blanket verification over unreceipted rows produce failures. A consistent fabricated
+receipt can still pass: this is a local consistency check, not fetch authentication.
+Timestamp provenance, live support for the claim and freshness require gate review.
+
+## Run and verify by hand
+
+From the repository root:
+
+```sh
+node bin/website-build-skill.mjs check-library test/fixtures/library-red
+node bin/website-build-skill.mjs check-library test/fixtures/library-green
+node --test test/library-check.test.mjs
+```
+
+Expect the RED fixture to exit 2 and name both unreceipted claims plus its blanket
+verification claim. Expect GREEN to exit 0 with counts. The fixtures are synthetic
+or inactive regression data, never live research evidence.
+
+## Source of truth
+
+The implementation is `src/library-check.mjs`. The research policy lives in
+`skills/website-build-skill/checklists/research.md`; receipt authoring is specified
+in `skills/website-build-skill/templates/evidence.md` and
+`skills/website-build-skill/playbooks/research-and-memory.md`.
+Tests live in `test/library-check.test.mjs`. Hosted and live-client behavior remains
+UNVERIFIED until an actual trial is separately authorized and recorded.

package/docs/METHOD.md

@@ -0,0 +1,32 @@
+# Method
+
+Research. Learn. Ingest. Execute: Match. Mock. Build. Prove. Ship.
+The [canonical skill](../skills/website-build-skill/SKILL.md) owns the method.
+
+| Stage | Owner | Reviewable result |
+| --- | --- | --- |
+| Research | Researcher | Saved library, thirteen-domain coverage, sources and gate receipt |
+| Learn and ingest | Every role | Reopened library, applied checklist and learning receipt |
+| Scope | Coordinator | Brief, capabilities and artifact ownership |
+| Match | Designer | Brand rules, tokens, conflicts and approved inferences |
+| Mock | Designer with Graphics | Three visual directions and a named human selection |
+| Choose and build | Builder | Smallest justified stack and selected implementation |
+| Prove | Builder, Designer, Optimizer | Accessibility, performance and discovery evidence |
+| Protect | Builder | Headers and exposed-surface checks |
+| Challenge | Different-family Reviewer | Read-only findings against a fixed candidate |
+| Ship | Coordinator then Builder | Authorized promotion, live checks and operations document |
+
+ASK DATE is the date of the user's request, fixed at engagement start.
+Researcher establishes it before intake using the [canonical rule](../skills/website-build-skill/playbooks/research-and-memory.md#ask-date-rule).
+A source publication/update date describes the source. An access date records an actual opening.
+Revalidation records whether a claim still applies and what was reopened. A freshness window limits reuse.
+A derived floor is a qualified lower bound, never proof of the actual day or later currency.
+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.
+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.
+
+The user owns the resulting library, claim ledger, domain checklists, decisions and handoffs.
+Keep them with the website project. The skill repository is the method, not storage for client work.

package/docs/PROVENANCE.md

@@ -0,0 +1,36 @@
+# Provenance
+
+The method's research prompts originate in two public posts by the repository's author:
+
+- [Research, learn, ingest, then execute](https://x.com/i/status/2095267280053735464): graphics research and evidence-led site review.
+- [Current design research and three brand-matched mockups](https://x.com/i/status/2097418846282145946): browser exploration, brand inputs and design selection before code.
+
+Attribution comes from the supplied source record; live post retrieval is UNVERIFIED here.
+The [inactive graphics original](../skills/website-build-skill/archive/graphics-design-original.md) retains its bytes and historical save instruction.
+It is provenance reading only and is excluded from active bundles and stage routes.
+The website research and site audit prompts are adaptations. They are not a recovered historical audit transcript.
+Reported historical measurements are not repeated as package evidence.
+Original package work uses [MIT](../LICENSE). The conduct text retains its own attribution and license.
+No third-party site screenshots, fonts or brand kits are included.
+
+## Reference ledger
+
+These links are research entrypoints, not evidence that this package was loaded in a client.
+Open current sources and record real source/access dates before relying on a claim.
+
+- [WCAG contrast](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html).
+- [Core Web Vitals](https://web.dev/articles/defining-core-web-vitals-thresholds).
+- [Search and AI features](https://developers.google.com/search/docs/appearance/ai-features).
+- [Browser examples](https://threejs.org/examples/).
+- [Host sources and settling checks](COMPATIBILITY.md).
+
+## Automation pin provenance
+
+The checkout v7.0.1 tag points to commit `3d3c42e5aac5ba805825da76410c181273ba90b1`.
+Source: [upstream tag](https://github.com/actions/checkout/releases/tag/v7.0.1), checked through the GitHub API in the baseline receipt.
+This identifies the pin; it is not an audit of the action or a hosted workflow run.
+
+The setup-node v7.0.0 tag points to commit `820762786026740c76f36085b0efc47a31fe5020`.
+Source: [upstream tag](https://github.com/actions/setup-node/releases/tag/v7.0.0), checked through the GitHub API in the baseline receipt.
+These tag checks identify pins only; they are not an audit of the actions. See the
+[baseline receipt](evidence/audit-baseline.json) for the separate hosted-check observation.

package/docs/TIPS.md

@@ -0,0 +1,18 @@
+# Tips
+
+1. Start with one audience and one primary action. A page needs a job before decoration.
+2. Give the agent approved brand files. If absent, supply profile and banner screenshots and review the inferences.
+3. Ask for three materially different mockups using the same copy. Select a named direction before code.
+4. Save the research library. A summary without sources cannot support the next worker's decisions.
+5. Reopen library files before each role. Send disagreements back to Researcher with claim IDs.
+6. Choose the smallest stack that meets the actual interactions and publishing needs.
+7. Make another page a data record and another brand a token set where the site permits it.
+8. Compute contrast for actual text/background pairs. A vivid accent can still be unreadable.
+9. Test the primary journey with keyboard, narrow viewport and reduced motion.
+10. Keep embeds behind accessible click-to-play facades and verify the initial network requests.
+11. Ask a different model family to challenge the fixed candidate. Reproduce findings before changing code.
+12. Preserve receipts and a memory packet. Proposed memory is not a saved state.
+13. Keep project work private and publish only the reviewed site artifact.
+14. Treat unavailable tools honestly. A wireframe is planning; a visual mockup requires viewable pixels.
+
+Next: [method](METHOD.md), [compatibility](COMPATIBILITY.md), [checklists](bundles/checklists.md).