website-build-skill 0.1.2 → 0.1.4

package/skills/website-build-skill/roles/researcher.md

@@ -97,12 +97,12 @@ Use Markdown for research outputs; record actual access dates and source dates
 separately. Unknown publication dates stay unknown, never invented.
 
 Use [the research prompt](../prompts/01-website-deep-research.md) as the single
-source for the thirteen-domain questions, output filenames and applicability rules.
+source for the fourteen-domain questions, output filenames and applicability rules.
 Read it before starting; survey each domain and preserve explicit exclusions with reasons.
 Expand relevant questions for the actual brief rather than treating the list as a ceiling.
 
 Use [the canonical freshness rule](../playbooks/research-and-memory.md#ask-date-rule)
-for the thirteen-domain table, date arithmetic, current-version triggers, same-day checks
+for the fourteen-domain table, date arithmetic, current-version triggers, same-day checks
 and prior-library pass. Copy that table into the project's staleness.md, with claim-level
 revalidation and the earliest-expiring domain. Never maintain a separate policy table here.
 
@@ -128,20 +128,21 @@ resolve the canonical record; never silently erase an earlier disagreement.
 
 ## YOUR OUTPUTS
 
-Write seven grouped Markdown files: 01-codebases-and-stacks.md,
+Write eight grouped Markdown files: 01-codebases-and-stacks.md,
 02-design-and-experience.md, 03-graphics-and-rights.md,
 04-accessibility-and-performance.md, 05-search-and-answers.md,
-06-security-and-delivery.md, and 07-measurement-and-operations.md under your library.
+06-security-and-delivery.md, 07-measurement-and-operations.md, and
+08-languages-and-code.md under your library.
 Write README.md with headline findings and each role's reading order; scope.md and
-coverage.md mapping all thirteen domains to files, checklists, applicability, and
+coverage.md mapping all fourteen domains to files, checklists, applicability, and
 blockers; sources.md with stable claim IDs, URLs, source/access dates, and scope;
 disagreements.md, query-plan.md, and unresolved-claims.md with next verification steps.
-Write all thirteen checklists named in the domains, using criterion, method,
+Write all fourteen checklists named in the domains, using criterion, method,
 expected evidence, source IDs, owner, status, and exclusion reason per check.
 Write website-qa-checklist.md and how-to-read-a-brand-kit.md so research is executable.
 Write surprises.md as a short sourced summary for the user, and learning.md as your
 record of learned rules. Every research output is Markdown with the dated opener.
-Write staleness.md with the canonical playbook's thirteen-domain table, claim/domain, ASK DATE,
+Write staleness.md with the canonical playbook's fourteen-domain table, claim/domain, ASK DATE,
 window, original access, last revalidation, next-check date, trigger, reason, owner,
 affected receipts, and the earliest-expiring domain and its ASK DATE-relative due date. Recheck volatile pricing,
 rights, APIs, host rules, and crawler/search claims on the day they will be used.
@@ -172,7 +173,7 @@ your self-check must cover the same evidence without claiming independent review
   backed by actual current source access. Do not restamp unrevalidated content.
 - No search means BLOCKED with query-plan.md and unresolved-claims.md, including
   for an existing library. Never ask the user for the date to clear a failed rung.
-All thirteen domains have an explicit disposition; a blank section is not coverage.
+All fourteen domains have an explicit disposition; a blank section is not coverage.
 Every relied-on disagreement is resolved by evidence or blocks the dependent choice.
 UNVERIFIED claims remain visible but cannot authorize work. Missing sources, dates,
 coverage, expired relied-on facts, or unsaved files mean BLOCKED, not qualified PASS.

package/skills/website-build-skill/roles/reviewer.md

@@ -32,12 +32,14 @@ disagreements.md, unresolved-claims.md, and staleness.md in that same directory.
 Verify the research gate and current revision before doing your job. Then read
 site-work/research/library/01-codebases-and-stacks.md,
 04-accessibility-and-performance.md, 05-search-and-answers.md,
-06-security-and-delivery.md, and 03-graphics-and-rights.md for rights checks.
+06-security-and-delivery.md, 08-languages-and-code.md, and
+03-graphics-and-rights.md for rights checks. Read site-work/coding-standards.md.
 Read all applicable library checklists, especially 06-accessibility.md,
-10-security.md and 13-legal.md. Read prompts/10-adversarial-pre-ship.md,
+10-security.md, 13-legal.md, and 14-code.md. Read prompts/10-adversarial-pre-ship.md,
 playbooks/data-and-templates.md, playbooks/security-headers.md,
-playbooks/accessibility.md, checklists/build.md, checklists/accessibility.md,
-checklists/security.md, checklists/ship.md, and templates/audit-brief.md.
+playbooks/accessibility.md, checklists/build.md, checklists/code-quality.md,
+checklists/accessibility.md, checklists/security.md, checklists/ship.md,
+and templates/audit-brief.md.
 Return your learning receipt with opened files, assumptions challenged, and checks.
 
 ## WHAT YOU MUST RESEARCH
@@ -108,6 +110,9 @@ Old dates may appear only as explicit history alongside current validated access
 Treat a confident undated claim as a finding, not a detail. Verify source dates,
 ladder provenance, due domains and later-day rechecks; return violations read-only.
 Check actual different-family evidence and the precise artifact reviewed. Challenge
+the code against checklists/code-quality.md and site-work/coding-standards.md,
+including pinned versions, deprecated APIs, support, commands, dependencies, secure
+coding, organization, and Builder's code-review evidence. Challenge
 input/URL/script escaping, empty IDs, shared state, auth and secrets where applicable,
 headers, rendered discovery, accessibility journeys, and assumptions in the brief.
 Return enough evidence for Builder to reproduce each asserted defect; otherwise

package/skills/website-build-skill/templates/evidence.md

@@ -16,7 +16,7 @@ Record the scope link, library revision, engagement identifier, producer role an
 | Field | Required value and evidence |
 | --- | --- |
 | claim_id | Stable identifier referenced by decisions, checks and findings. |
-| domain | One of the thirteen research domains, with additional scoped concerns as needed. |
+| domain | One of the fourteen research domains, with additional scoped concerns as needed. |
 | statement | Exact bounded claim, including relevant version, tier, consumer or use. |
 | kind | Evidence, inference, proposed default, measurement, or UNVERIFIED. |
 | source_url | Opened authoritative URL; a search snippet does not satisfy this field. |

package/src/cli.mjs

@@ -8,7 +8,7 @@ check-library <site-work-dir> (read-only receipt validation)
 --solo | --team  --target ${Object.keys(targets).join('|')}
 --dir <path>  --scope project|user  --output-dir <path>
 --yes  --dry-run  --receipt <path>  --uninstall  --help  --version
---bundle-dir <path> (Hermes TEAM only)
+--bundle-dir <path> (Hermes TEAM only; relative to the installed skill folder)
 Headless installs require explicit mode, target and --dir.
 Activation remains UNVERIFIED.`;
 

package/src/validate.mjs

@@ -351,6 +351,9 @@ export function check(root, options = {}) {
     if (/they are ready/i.test(choice)) issues.push('CHOICE_HONESTY:no installer creates a running worker');
     if (!p.bin && !/one-command install is planned/i.test(choice)) issues.push('CHOICE_HONESTY:manual-setup statement missing');
     const settings = read(root, 'REPO_SETTINGS.md');
+    const description = settings.split(/^## Description\r?$/m)[1]?.split(/^## /m)[0]
+      .split(/\r?\n/).filter(line => line.trim() && !/^- \[[ x]\] /.test(line)).join('\n');
+    if (description !== p.description) issues.push('DESCRIPTION_DRIFT:REPO_SETTINGS.md');
     const topics = settings.split('## Topics')[1].split('## Creation')[0].split('\n').filter(s => /^- [a-z0-9-]+$/.test(s)).map(s => s.slice(2));
     if (JSON.stringify(topics) !== JSON.stringify(p.keywords) || topics.length > 20 || topics.some(t => !/^[a-z0-9]+(?:-[a-z0-9]+)*$/.test(t) || t.length >= 50)) issues.push('TOPICS:invalid or mismatched keywords');
     if (p.description.length >= 350) issues.push('DESCRIPTION:too long');