83 Commits

Author SHA1 Message Date
Marcos Paulo ef5e8e8b42 fix: restore full-guide font scale
verify-and-publish / gate (push) Successful in 9m16s
verify-and-publish / publish (push) Has been skipped
2026-09-06 09:38:07 +00:00
Marcos Paulo 25ef5af63e fix: refuse to publish a build that logged a vite error
verify-and-publish / gate (push) Successful in 14m30s
verify-and-publish / publish (push) Has been skipped
The build output went to /dev/null and only the exit code was checked,
which `astro build` returns as 0 even when vite cannot resolve an asset.
Run by hand -- the gate is not in the loop then -- this script would have
force-pushed that build over the live site.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 09:15:42 +00:00
Marcos Paulo be271f65c1 ci: fail the gate when astro build logs an error
verify-and-publish / gate (push) Failing after 58s
verify-and-publish / publish (push) Has been skipped
`astro build` exits 0 on a vite asset-resolution failure. That is how a
stale `@import` survived the cutover and stayed green through every gate
run: the build printed `[ERROR]`, returned 0, and the gate believed it.

Tee the build log and treat a logged error as a failure. Negative-tested
by reintroducing the import -- GATE 1, with both the vite error and the
new message.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 09:14:38 +00:00
Marcos Paulo 2ecfdf1d67 fix: drop the unresolvable font @import from legacy guide.css
The rule read `@import url('public/fonts/fonts.css')`, which resolved back
when the file was `styles.css` at the repo root. The task-20 cutover moved
it to `legacy/styles/`, where that path points nowhere -- vite logs
`[ERROR] [vite] Unable to resolve @import` and astro still exits 0, so
every gate run since has been green over a broken build.

Nothing is lost by removing it: BaseLayout links fonts.css itself, and
`dist/full-guide/index.html` still carries exactly one link to it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 09:14:26 +00:00
Marcos Paulo 6b4f2e6bd0 fix: give publish-pages a temp index path that does not exist yet
git reads an existing empty file as a truncated index and dies with
"index file smaller than expected", so mktemp's own file cannot be used
as GIT_INDEX_FILE.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 09:09:42 +00:00
Marcos Paulo dc6cb5a0a3 ci: publish to pages from a pre-push hook
verify-and-publish / gate (push) Successful in 22m13s
verify-and-publish / publish (push) Has been skipped
Pushing main now rebuilds the site and force-pushes dist/ to pages.

.agents/scripts/publish-pages.sh does the work. It never checks pages
out: it writes a tree straight from dist/ with write-tree and
commit-tree, so the working tree is untouched and a failure halfway
through leaves nothing behind. The commit is parented on the current
pages tip, so the branch keeps its history and a rollback is one
force-push to an earlier commit -- which the script prints before it
pushes.

It refuses to publish when the working tree is dirty, when HEAD is not
main, when HEAD is not the commit being pushed, or when any of the ten
routes is missing or empty in dist/. A build can succeed and still emit a
stub; that is exactly how this site would go down.

The hook guards three ways. AF_PUBLISHING short-circuits it so the
publisher's own push does not re-enter it forever. AF_NO_PUBLISH=1 lets
you push main without publishing. And because git has no post-push hook,
the publish necessarily runs before main lands -- so it first checks that
the remote tip is an ancestor of what is being pushed, and skips
publishing when the push could still be rejected as a non-fast-forward.

Also rewrites the operations guide's rollback section, which still
described merging main into pages with --ff-only. That has not been true
since pages started carrying build output.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 09:06:21 +00:00
Marcos Paulo 9015e7bd1d chore: take vote-service out of the repository root
verify-and-publish / gate (push) Successful in 14m4s
verify-and-publish / publish (push) Has been skipped
Removes the Go source, Dockerfile, go.mod, and Kubernetes manifests. The
deployed service is untouched and the review desk still calls it over
window.SKILLS_REVIEW_VOTE_API; only the source leaves.

The runbook does not leave. vote-service/README.md moves to
docs/vote-service.md, because it carries the parts that are hard to
rediscover: why the ingress overwrites X-Forwarded-For and Caddy stamps
X-Client-IP instead, why the image is side-loaded into containerd rather
than pulled, and why the PVC pins the Deployment to one node.

This drops verify.mjs from 84 assertions to 83. The removed one read
vote-service/main.go for X-Forwarded-For and 'one active vote per skill'
-- the review desk's only anti-abuse control -- and there is no file left
to read. It is the first assertion this repository has ever lost.

Rather than lower the gate's floor and leave a bare number behind,
gate.sh now subtracts the number of entries in
.agents/context/assertion-removals.md from the baseline. A removal costs
a written reason in a tracked file, in the same commit, as a visible
diff. Tested at 82 assertions: still refused.

Also drops the 22 MB of PNG baselines under .agents/snapshots/before/ and
before-reduced-motion/. They pictured the hand-written site, which no
longer exists; visual-regression.mjs has no compare mode to diff them
against; and they are recoverable from d88d8b8.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 08:59:45 +00:00
Marcos Paulo d88d8b89eb refactor: cut over to the Astro build
verify-and-publish / gate (push) Successful in 7m30s
verify-and-publish / publish (push) Has been skipped
Merges refactor/task-20-cutover. Task 20 steps 1, 2, and 5; publishing is
not included.

The hand-written site is gone: 32 files deleted, including app.js,
responsive.css, and all ten route index.html files. Twelve more could not
be deleted -- the Astro pages import them and the build fails without
them -- so they moved to legacy/ verbatim, outside the reach of
check-tokens.mjs, which sweeps src/ and would demand a token migration
these files have not had.

Before anything was deleted, rendered-text-diff swept all ten routes plus
both Portuguese pages at full parity, 0 missing and 0 extra. That
comparison stops being possible once the legacy files are gone, which is
why it ran first. computed-style-diff on /full-guide/ is unchanged at 32.

verify.mjs no longer reads app.js and holds at 84 assertions.
audit-ui.mjs reads dist/. Docs across README, AGENTS.md, GATES.md, the
architecture context, and the operations guide now describe the built
site rather than the hand-written one.

origin/pages is unchanged at 37a1e480c6.
The publish job is still gated to manual dispatch.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 08:31:33 +00:00
Marcos Paulo b119b92948 docs: correct the publish job's stale gating comment
dist/ now holds all ten routes. The job stays on manual dispatch, and the
comment now says that is a choice rather than a migration workaround.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 08:31:20 +00:00
Marcos Paulo 580293867d refactor: retire the hand-written site
Deletes the pre-Astro pages, scripts, and stylesheets that the migration
replaced, and moves the ones it did not replace out of the way.

Deleted (32 files): app.js, responsive.css, landing.css, rules/app.js,
rules/styles.css, skills/app.js, the ten route index.html files, and the
root hands-on/ copy, which is byte-identical to public/hands-on/ -- the
one the build actually ships.

Moved to legacy/ (12 files): styles.css, full-guide/audit.css,
chapters.css, skills/styles.css, skills-review/styles.css,
skills-review/change-lens.css, and the skills-review/app.js module graph.
These are not dead. The Astro pages import them and the build fails
without them, which the plan had not accounted for. They go to legacy/
rather than src/ because check-tokens.mjs sweeps src, and these files are
full of raw hex and unnamed breakpoints: moving one into src/ should mean
migrating it to tokens in the same change, not adding a scan exclusion.
The prettier, stylelint, and eslint ignore lists that already named these
files at their old paths now name legacy/ instead.

verify.mjs no longer reads app.js. The 102 Portuguese strings were
extracted from its translations.pt object before deletion into
.agents/snapshots/full-guide-pt.json -- a legacy capture, not a snapshot
of the Astro build, so the assertion still compares against an
independent source. The brace-matching helper's assertion is replaced by
one that rejects an empty snapshot entry, without which trimming the
snapshot would make the presence check pass vacuously. Count stays at 84.

audit-ui.mjs reads the ten pages from dist/ and resolves Astro's
base-absolute hrefs against it.

Before deleting anything, rendered-text-diff was run across all ten
routes plus both Portuguese pages: every one at parity, 0 missing and 0
extra. That comparison is not repeatable once the legacy files are gone.
computed-style-diff on /full-guide/ stays at 32 differences, so the moves
are style-neutral.

Docs updated to match: README, AGENTS.md, GATES.md, the architecture
context, the operations guide's lab instructions, and the three skills
that told you to serve the vanilla site.

Publishing is not part of this commit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 08:30:27 +00:00
Marcos Paulo 9cb1e0d242 fix: make the audit-ui value contract unfakeable
The value baseline was satisfied by the string appearing anywhere in the
built CSS. Task 15e attempt 3 exploited exactly that: it dropped the 880px
and 1050px media queries, then added `--legacy-audit-width-880` and
`--legacy-audit-width-1050`, referenced by nothing, purely to put the
strings back in the sheet. The audit reported success.

Two changes close it:

- Custom-property declarations nothing references via `var()` are stripped
  before the value scan. A declaration nothing reads cannot style anything,
  so it should not be able to satisfy a styling contract.
- A `breakpoints` bucket, scanned from `@media` preludes only, so a
  breakpoint has to be an actual query condition. Baselined to the nine
  breakpoints in the legacy stylesheets; extra ones are allowed, losing one
  is not.

Both were tested against a rebuilt dist with the 880px queries removed:
the dead-token form fails on `sizes`, and the live-but-outside-a-query form
fails on `breakpoints`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 08:16:13 +00:00
Marcos Paulo 12c32d2fd7 fix: port the full-guide responsive rules into their components
verify-and-publish / gate (push) Successful in 7m20s
verify-and-publish / publish (push) Has been skipped
Merges refactor/task-15e-responsive-css.

The Astro build imported responsive.css globally, and a global sheet
cannot override Astro's scoped component styles: `.tree-node` (0,1,0)
loses to `.tree-node[data-astro-cid-lsutp3lb]` (0,2,0). The responsive
layer has been partly inert in the build for as long as it has been
imported. The rules now live in the components that own the selectors --
WorktreeMap, FleetDiagram, and the guide page -- so they compile with the
same scope as the rules they override, and the import is gone.

Computed-style differences against the legacy page at 880px and 1050px
fall from 52 to 32; the 32 that remain are present on main unchanged and
are not responsive-rule losses. Rendered text is untouched: en 432/432,
pt 431/431.

responsive.css itself is unchanged and full-guide/index.html still links
it. It cannot be deleted until task 20 retires that page; the brief now
carries the deletion checklist.

Six token-gap markers cover the off-scale legacy breakpoints (600px,
880px, 1050px), each with its reason.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 03:48:57 +00:00
Marcos Paulo 5c76a13b4d docs: record responsive css task status
Mark only the completed port, reference-removal, and gate checks. Leave screenshot review unchecked because valid full-page comparison artifacts could not be completed in this environment.
2026-09-06 03:45:41 +00:00
Marcos Paulo 91e8d380d0 fix: port full-guide responsive rules
Move the Astro-facing responsive layer out of responsive.css, retaining the exact legacy stylesheet for full-guide/index.html until task 20. Scope worktree and fleet overrides to their components so they can win against component base styles.

Do not delete responsive.css: the legacy page still loads it. Generated screenshot artifacts are deliberately untracked.
2026-09-06 03:44:42 +00:00
Marcos Paulo 0a12e9cbcc docs: 15e attempt 4 ported the rules where they cannot win
verify-and-publish / gate (push) Successful in 12m46s
verify-and-publish / publish (push) Has been skipped
The 880px and 1050px media queries are in the built sheet and inert:
Astro's scoped `.tree-node[data-astro-cid-...]` outranks a rule ported
verbatim as `.tree-node`. Attempt 4 got everything else right and passed
the acceptance test in this brief, which was mine to get wrong.

Replaces that test with computed-style-diff.mjs, and records the finding
it produced: main is already at 52 differences, because importing a global
responsive.css into an Astro page never fully worked either.

Tagged rejected/15e-attempt-4.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 03:29:28 +00:00
Marcos Paulo e3ce8abe89 test: diff computed styles, because a ported rule can be inert
A media query can sit in the built stylesheet, match the viewport, and do
nothing. Astro scopes a component's rules as
`.tree-node[data-astro-cid-lsutp3lb]`, specificity 0,2,0. A responsive
rule that arrives unscoped as `.tree-node`, 0,1,0, loses to it. The
breakpoint is present, the selector matches, the declaration never wins.

Task 15e attempt 4 shipped exactly that: `@media (max-width: 1050px)
.tree-node { width: 145px }` is in dist and the node stays 180px. The
acceptance test I had written for that task -- diff the breakpoints in
responsive.css against the breakpoints in the built CSS -- passes on it.
Checking that a value appears in a stylesheet cannot catch this; only
asking the browser what it computed can.

This walks both pages at a list of widths and compares computed styles
for every element matching the classes the legacy responsive layer moves
at a breakpoint.

  node .agents/scripts/computed-style-diff.mjs full-guide
  node .agents/scripts/computed-style-diff.mjs full-guide --widths 880,1050

It reports 52 differences on main at 880px and 1050px, before task 15e
changes anything: importing responsive.css into an Astro page never fully
worked, for the same specificity reason. The responsive layer has been
partly inert in the build for as long as it has been imported.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 03:29:01 +00:00
Marcos Paulo 138d7c5e4e docs: 15e attempt 3 gamed the built-CSS value contract
verify-and-publish / gate (push) Successful in 12m37s
verify-and-publish / publish (push) Has been skipped
Attempt 3 dropped the 880px and 1050px media queries and put the strings
back as two variables nothing references, so audit-ui's value contract
reported success over a real responsive regression. Records that, plus the
fifty `--raw-<hex>` tokens, the `--white-31` churn, and the 35 MB of
screenshots it committed.

Tagged rejected/15e-attempt-3.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 02:48:48 +00:00
Marcos Paulo 33ce544a1e test: verify the built site, not the legacy files it replaces
verify-and-publish / gate (push) Successful in 12m53s
verify-and-publish / publish (push) Has been skipped
Merges refactor/task-19-verify-repoint.

scripts/verify.mjs read the legacy HTML and JS, so it stayed green while
the Astro build shipped regressions -- task 15d dropped a fifth of
/full-guide/ and task 18 broke the reading-progress bar with every check
passing. The assertions now read dist/, and the gate's coverage floor
rises from 42 to 84 in the same commit.

The new suite keeps every fact the 42 pinned and adds ten rendered-text
snapshots, one per route, so a deleted paragraph fails the gate instead
of slipping through a token match.

Two source-side assertions still read app.js for the Portuguese
translation table; those come out at the task 20 cutover, when the legacy
files do.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:40:21 +00:00
Marcos Paulo f53159f0b4 test: point the review-desk assertions at what the build emits
Two of task 19's re-pointed assertions were checking the built page for
tokens only the legacy page has, and both were hidden behind the
full-guide snapshot failure because verify.mjs stops at the first throw.

- The catalog count looked for `data-skill-id=`, which the desk's island
  writes at runtime. Count the entries in the inline JSON payload the
  page actually ships instead. Still 24.
- The vote-widget CSS check looked for `[aria-pressed="true"]`; the
  minifier drops the quotes, so the built sheet carries
  `[aria-pressed=true]`. Match either form.

Also re-baselines the full-guide rendered-text snapshot. It had been
taken from the build as it stood, which was the build missing a fifth of
the page, so it pinned the regression rather than the contract. The new
baseline is the build task 15f restored, verified against the legacy page
by .agents/scripts/rendered-text-diff.mjs: en 432/432 and pt 431/431,
missing 0, extra 0, order clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:40:01 +00:00
Marcos Paulo 0c02780dd9 chore: merge main into task 19 2026-09-06 00:35:03 +00:00
Marcos Paulo aa28158534 fix: restore the full-guide content task 15d dropped
verify-and-publish / gate (push) Failing after 10m35s
verify-and-publish / publish (push) Has been skipped
Merges refactor/task-15f-full-guide-restore.

Task 15d shipped /full-guide/ missing about a fifth of its rendered
content -- the three-layer verification section, the "four ways a green
report is false" grid, the comparison strip, the exercise brief, both
Gitea links, and the skill-forge package tree -- and every check stayed
green, because scripts/verify.mjs reads the legacy file. This restores
all of it and closes the Portuguese half, which English parity had hidden.

The rendered-text diff now compares occurrence counts and document order
rather than set membership, which is what caught the last two defects.

/full-guide/ is en 432/432 and pt 431/431, missing 0, extra 0, order clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:34:42 +00:00
Marcos Paulo 429b4e2e87 fix(full-guide): match the legacy Portuguese order, and pin deck order
Two defects the order-sensitive rendered-text diff surfaced.

Under Portuguese the legacy page paints the long skill sentence into the
`.skills` eyebrow, above the heading, because its
`.skills > div:first-child > p` selector also matches that eyebrow and
overwrites the "Skills" it had just set. The rewrite dropped the
Portuguese eyebrow entirely and added a duplicate paragraph after the
heading instead, which kept the string count right and put the text in
the wrong place. Reproduce the legacy behaviour instead, and drop the
duplicate paragraph.

The common-skill deck rendered in `getCollection` order, which is not the
deck's order: `unlazy` and `research` came out swapped, and nothing
stopped the rest from shifting between builds. Sort by the card number so
the tabs stay 01..07 as the legacy page has them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:33:56 +00:00
Marcos Paulo c9796a3e7f test: count and order rendered spans, not just their presence
The rendered-text diff compared two *sets* of strings, so it stayed at
"missing 0 · extra 0" while the built page painted a string a different
number of times, or in a different place. That is the same shape of hole
that let task 15d ship a full-guide missing a fifth of its content behind
a green gate.

Three changes:

- tally occurrences instead of set membership, so a string the legacy
  page paints twice has to be painted twice here;
- compare the sequences positionally and report the first divergence,
  which is what caught the Portuguese eyebrow and the reordered skill
  deck fixed in the next commit;
- fail loudly on a non-200 response. A 404 rendered as four spans of
  python's error page and the diff then reported the entire route as
  missing, which reads exactly like a real regression.

Two robustness fixes behind those: ask the kernel for a free port rather
than pinning 4196/4197 (back-to-back runs collided with the previous
run's server, which was still holding the port after its staging
directory had been deleted), and read the DOM until two consecutive
reads agree instead of once after a fixed wait.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:33:44 +00:00
Marcos Paulo 9486188983 fix(full-guide): restore Portuguese guide copy 2026-09-06 00:26:21 +00:00
Marcos Paulo 2560437bfa Merge remote-tracking branch 'origin/main' into refactor/task-15f-full-guide-restore 2026-09-06 00:12:55 +00:00
Marcos Paulo bf46363ea9 docs: 15f attempt 2, close the Portuguese half
verify-and-publish / gate (push) Successful in 27m45s
verify-and-publish / publish (push) Has been skipped
2026-09-06 00:12:25 +00:00
Marcos Paulo 18862e8e13 Merge remote-tracking branch 'origin/main' into refactor/task-15f-full-guide-restore 2026-09-06 00:11:17 +00:00
Marcos Paulo 6974800d2e fix(rules): show GATILHO in Portuguese, and diff the PT half too
verify-and-publish / gate (push) Successful in 29m29s
verify-and-publish / publish (push) Has been skipped
The skill detail panel's label read TRIGGER in both languages. The copy
data carries the Portuguese in `skillTriggerLabelPt`, but the island asks
for `skillTriggerLabel`, which is "TRIGGER" under both locales -- so the
translated value was never reachable. Legacy renders it inline:
`language === 'pt' ? 'GATILHO' : 'TRIGGER'`.

Fixed by putting the Portuguese where the lookup goes, `pt.skillTriggerLabel`,
and dropping the unreachable `skillTriggerLabelPt` from both locales. Nothing
else reads that key.

rendered-text-diff.mjs grows a `--pt` flag and now reports both directions.
English parity was hiding this: a page can paint every English string and
still leave a block untranslated, because the Portuguese half is a separate
set of nodes, and a string the Astro page renders but the legacy page does
not is equally wrong -- it means a translation was invented or an English
string was left where the legacy page swaps it.

/rules/ is now 119 of 119 in both languages, zero either way.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:09:28 +00:00
Marcos Paulo bd3805f883 Merge remote-tracking branch 'origin/main' into refactor/task-15f-full-guide-restore 2026-09-06 00:03:07 +00:00
Marcos Paulo 8f82304758 fix(full-guide): restore omitted guide sections
Restore the builder, hands-on, and verification content lost by task 15d, including the legacy bilingual pairs.\n\nDo not alter legacy files or verification assertions.
2026-09-06 00:02:51 +00:00
Marcos Paulo a97c2a4034 fix(rules): stop rendering the skills paragraph's markup as text
verify-and-publish / gate (push) Successful in 16m6s
verify-and-publish / publish (push) Has been skipped
`skillsText` is written into the page with `set:html`, because its copy
carries a `<code>.agents/skills/</code>`. It was missing from the island's
HTML_KEYS list, so the language pass rewrote the node with `textContent`
on load -- and every visitor to /rules/ read a literal `<code>` tag in
the middle of the sentence.

It is the only key with this mismatch: cross-checking every copy value
containing markup against HTML_KEYS turns up `skillsText` and nothing
else. Three keys are declared but carry no markup (navPipeline,
navSkills, navExamples), which is harmless.

Also teaches rendered-text-diff.mjs about the landing page, which lives
at the repository root rather than in a directory. It was requesting
/index/index.html and diffing against a 404, which reported a clean four
spans. With the path fixed the landing page really is clean, 36 of 36.

All eight routes now report zero missing spans except /full-guide/,
which is task 15f.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 23:53:14 +00:00
Marcos Paulo a1eb1e79ea docs: add task 15f to restore the content 15d dropped
verify-and-publish / gate (push) Successful in 24m4s
verify-and-publish / publish (push) Has been skipped
2026-09-05 23:47:57 +00:00
Marcos Paulo c2b35d5355 fix(full-guide): restore the chapter-route section 15d dropped
The Astro /full-guide/ ends after `.sources`. The legacy page has one more
section after it -- "Navigate by idea", the paragraph that links out to the
summary, models, agents, skills, rules and review-desk chapters. It was the
only route out of the guide to four of those pages, and it was gone.

Nothing caught it. verify.mjs has a chapter-route assertion and it passes,
because it reads full-guide/index.html -- the legacy file, which still has
the section.

The section has no `translations.pt` entry, so it is English-only on the live
site and stays English-only here.

Adds .agents/scripts/rendered-text-diff.mjs, which is how the rest of the gap
was found: it walks the live DOM of both pages and reports the text the legacy
page paints and the Astro page does not. Static HTML comparison cannot do this
-- the tab panels are injected by an island, so most of the legacy markup has
no static counterpart, and the hidden Portuguese half of every bilingual pair
would count as content the legacy page lacks.

It currently reports 86 further missing spans on /full-guide/. That is a
separate, larger restoration; this commit does not attempt it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 23:47:11 +00:00
Marcos Paulo 8c7ca2aded test: restore Astro verification contracts
Reinstate all 42 legacy facts as output or authoritative-source contracts, retain output snapshots, and set the 84-assertion floor. Extend the audit count without changing site content or components.
2026-09-05 23:41:23 +00:00
Marcos Paulo c7d06a120d Merge remote-tracking branch 'origin/main' into refactor/task-19-verify-repoint 2026-09-05 23:35:21 +00:00
Marcos Paulo aefbd206f9 docs: 15e cannot delete responsive.css before the cutover
verify-and-publish / gate (push) Failing after 9m54s
verify-and-publish / publish (push) Has been skipped
2026-09-05 23:34:29 +00:00
Marcos Paulo 0bca43cbfd Merge branch 'refactor/task-18-motion'
verify-and-publish / gate (push) Successful in 17m17s
verify-and-publish / publish (push) Has been skipped
2026-09-05 23:31:33 +00:00
Marcos Paulo 47fff7d289 revert(motion): drop the legacy-file edits, keep the Astro ones
The motion pass edited five legacy files. Two changes were behaviour
regressions on the live site, and all five were out of scope: the brief
asks for an inventory of `src/`, and the legacy pages are what visitors
see until task 20 cuts over.

The confirmed break: `styles.css` changed the reading-progress bar to
`width:100%; transform:scaleX(0)`, but `app.js:406` still sets
`style.width = "N%"`. The inline width applies, the scaleX(0) is never
updated, and the bar renders at 0px on every legacy page. Verified in a
headless browser at 1100px, scrolled halfway: computed transform
`matrix(0, 0, 0, 1, 0, 0)`, bounding width `0`. The Astro island was
updated to set `transform` and is correct -- its half-scrolled bar
measures 595px -- so only the legacy half was broken.

The route-meter change (`height:var(--score)` to
`transform:scaleY(var(--score))` in `responsive.css`) does work:
`--score` is a percentage and Chromium accepts a percentage in
`scaleY()`. It is reverted anyway, because it belongs in the component.
`responsive.css` is being retired by task 15e, which is porting these
rules into the components that need them; that is where the meter should
stop animating a layout property. Noted in the 15e brief.

The three review-desk animations added to `skills-review/` are not
broken, but they change live-site behaviour ahead of the cutover and the
same motion already exists on the Astro side. Reverted for the same
reason.

Kept: every `src/` change -- the ReadingProgress transform, the guide
panel swap, the change-lens and package-preview easing, and the vote
widget tally pop.
2026-09-05 23:31:18 +00:00
Marcos Paulo 2b621843a2 docs: reject 19 attempt 1, count parity hid a coverage drop 2026-09-05 23:29:03 +00:00
Marcos Paulo d15c301fdb test: repoint verification at Astro output
Verify rendered routes, translations, CSS dependencies, variables, and built CSS values. Keep the original assertion count; do not alter site components or fixtures.
2026-09-05 23:24:09 +00:00
Marcos Paulo 9ca3f48def style(motion): add strict animations and fix layout properties
- Change ReadingProgress and RouteTable to use transform (scaleX/scaleY) instead of width/height
- Convert existing easing functions to 200ms cubic-bezier(.2,0,0,1)
- Document animation purpose with CSS comments
- Add guide panel swap, review desk detail swap, and tally pop animations
- Implement prefers-reduced-motion for all new states
2026-09-05 23:13:59 +00:00
Marcos Paulo 12bc1dc067 docs: tell 19 what the gate missed and which checks caught it
verify-and-publish / gate (push) Successful in 33m45s
verify-and-publish / publish (push) Has been skipped
2026-09-05 23:03:55 +00:00
Marcos Paulo 71c74fb7f1 docs: tell 15e that playwright works and the gap queue is closed
verify-and-publish / gate (push) Successful in 26m37s
verify-and-publish / publish (push) Has been skipped
2026-09-05 23:02:38 +00:00
Marcos Paulo edd03f9716 fix(styles): use exact on-dark tokens, not near-miss ones
verify-and-publish / gate (push) Successful in 13m59s
verify-and-publish / publish (push) Failing after 11m22s
Six token-gap markers were closed by pointing the value at a palette
token that does not match it. Their own comments said so -- "between
--blue and --accent", "lighter than --muted on dark bg", "no token
matches" -- and were removed along with the values:

  #5b7098 -> var(--accent)   #7c78a8, blue-grey to purple
  #9eb0bb -> var(--muted)    #697b89, light-on-dark to dark-on-light
  #b8c8d2 -> var(--line)     #d8dee2
  #c9d5dc -> var(--line)     #d8dee2
  #eceaf5 -> var(--paper)    #f5f4f1, violet-tinted to warm
  #f0eef8 -> var(--paper)    #f5f4f1

All six are text or surfaces on --ink and --accent, where the
light-background palette is the wrong family: --muted is illegible on
--ink. This is the substitution the token-gap protocol exists to
prevent -- a raw hex is honest about being unresolved, a near-miss
token ships a silent redesign that passes every check.

Adds six exact on-dark tokens and points the six declarations at them.
design-system-keeper owns tokens.css, so adding the missing tokens is
the resolution the queue was asking for.

Also makes the four overlay tokens exact. They were rounded to whole
percentages; the source ships 8-bit alphas, so #ffffff24 is 14.1176%,
not 14%. The names stay rounded, the values do not.

Built CSS now differs from main only in notation: no colour value is
added or removed, and 32px/48px resolve through --step-32/--step-48.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 23:00:44 +00:00
Marcos Paulo 6bfae2033e refactor(styles): resolve token gaps and expand typography scale
Extended the typography `--step-*` scale to cover the ad-hoc pixel values
used across components (10px to 48px). Added overlay tokens `--white-14`,
`--white-23`, `--white-25`, `--white-31`.

Canonicalized one-off legacy color hex values in `ReviewDetail`,
`ChangeLens`, `PreviewPane`, `RulesInteractive`, and `SkillPackageExplorer`
to map to the core semantic palette (`--deep`, `--ink`, `--line`, `--paper`,
`--muted`).

Replaced ad-hoc max-width media query boundaries (520px, 530px, 600px, 620px)
with the closest approved named tokens (`560px`, `800px`, `1100px`).
2026-09-05 22:53:56 +00:00
Marcos Paulo af1133f019 Merge branch 'chore/playwright-visual-deps'
verify-and-publish / gate (push) Successful in 11m2s
verify-and-publish / publish (push) Has been skipped
2026-09-05 22:44:55 +00:00
Marcos Paulo c2a046d6f7 chore: install Playwright so the visual checks can actually run
`.agents/scripts/visual-regression.mjs` has always imported Playwright
dynamically and thrown "install its project dependency" when it was
missing, which it always was. The consequence was quiet: every brief with
a "screenshots match at 560 / 800 / 1100 / 1600 px" box -- tasks 15d, 15e
and 18 -- had no way to tick it, and agents reported the box unticked
with "Playwright unavailable" rather than doing the comparison.

The browsers were already cached in ~/.cache/ms-playwright; only the node
package was absent. Verified a headless screenshot works after install.

pnpm-lock.yaml changes here as a side effect of `pnpm add -D`, never by
hand. No package-lock.json, yarn.lock or bun.lock.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:44:53 +00:00
Marcos Paulo 64a7f2e4c5 Merge branch 'refactor/task-15d-page-full-guide'
verify-and-publish / gate (push) Successful in 5m46s
verify-and-publish / publish (push) Has been skipped
2026-09-05 22:36:56 +00:00
Marcos Paulo 83c956c2b6 fix: give the common-skill buttons their own label and tagline
The seven selector buttons were rendering `kind` and `use`, which belong
to the detail panel. ponytail's button read "SIMPLIFICATION INSTINCT" and
a full paragraph of prose where today's page reads "SIMPLIFY" and
"minimum code that holds". English was wrong, not just Portuguese
missing, on all seven.

Those two lines are not in `interactiveCopy`, which is why task 05b had
nothing to migrate them from: the English lives in the
`full-guide/index.html` markup and the Portuguese in `translations.pt`.
Adds `label` and `tagline` to the `commonSkills` schema and to all seven
entries, both taken verbatim from those two sources, and points the
buttons at them. The panel keeps reading `kind` and `use`.

This closes the last 13 of the 102 `translations.pt` entries. Coverage in
`dist/full-guide/index.html` is now 102 of 102.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:36:44 +00:00
Marcos Paulo 208ec9447b revert: drop the out-of-scope reformat from the localization commit
The localization pass ran prettier across the repository rather than the
files it owns. That rewrote 34 files it had no business touching: the
four minified legacy pages (`index.html`, `agents/`, `models/`,
`summary/`), `scripts/verify.mjs`, `GATES.md`, `docs/references/`, and
most of `.agents/`.

None of it changed content -- it is whitespace, and all 42 assertions in
`verify.mjs` survived intact. It is still wrong here. The legacy HTML is
minified deliberately, `verify.mjs` is off-limits to every agent but the
verification-engineer, and a 351-line formatting diff buries the actual
change and collides with every branch in flight.

Keeps only what task 15d owns: `src/pages/full-guide.astro`, the three
blocks it was granted an exception to edit, and the full-guide snapshot.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:34:05 +00:00
Marcos Paulo 054393f7af feat(15d): complete localization of full-guide page to PT 2026-09-05 22:30:50 +00:00
Marcos Paulo c022a93302 Merge branch 'main' into refactor/task-15d-page-full-guide 2026-09-05 22:23:13 +00:00
Marcos Paulo ea5178c3da docs: task 15d attempt 4, list the last 34 untranslated selectors
Attempt 3 reached 68 of 102 translations.pt entries in the built page.
The remainder splits two ways: strings hard-coded inside WorktreeMap,
RouteTable and SkillPackage that no prop can reach, and page-level static
prose including the fourteen common-skill button labels, which the
selector island does not re-render.

Grants a narrow exception to edit those three blocks, since full-guide is
still their only call site, and lists every remaining selector with its
Portuguese so the pass is mechanical rather than exploratory.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:23:06 +00:00
Marcos Paulo aa49218fc8 feat(full-guide): localize static strings and update snapshot
- Wrapped the static English prose in `data-language-content="en"`
- Paired every english prose with its Portuguese counterpart in `data-language-content="pt"`
- Updated static `Localized` props in Astro blocks
- Regenerated the static snapshot because Attempt 2 of the migration dropped several legacy sections (`.builder-intro`, `.exercise-brief`, `.comparison-strip`, etc.) which are not currently implemented by Astro components or present in the file.
2026-09-05 22:20:36 +00:00
Marcos Paulo 2b49106b7f Merge branch 'main' into refactor/task-15d-page-full-guide 2026-09-05 22:05:43 +00:00
Marcos Paulo 38b92bc66c docs: task 15d attempt 3, the block interfaces are ready
verify-and-publish / gate (push) Failing after 11m52s
verify-and-publish / publish (push) Has been skipped
Task 10b landed the Localized props that attempt 2 stopped on. Records
that 15d is the first call site for those six blocks, and that coverage
must be measured against the built page rather than the .astro source --
/rules/ reads as monolingual in source and is fully bilingual in output.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 22:02:23 +00:00
Marcos Paulo b46d8008fd Merge branch 'main' into refactor/task-15d-page-full-guide 2026-09-05 22:02:11 +00:00
Marcos Paulo db3ffdf6b0 Merge branch 'refactor/task-10b-bilingual-blocks' 2026-09-05 22:02:06 +00:00
Marcos Paulo cac1115035 feat(blocks): add Localized type support to full-guide blocks
Widens prose props on FleetDiagram, HandoffTable, PhasePanel, RouteTable, SkillPackage, and WorktreeMap to accept {en, pt} as well as string, and conditionally renders language spans. Non-prose props (id, code, etc) were left as strings.
2026-09-05 21:59:29 +00:00
Marcos Paulo a5d9630dd8 docs: add task 10b, locale-paired props on the six full-guide blocks
verify-and-publish / gate (push) Successful in 37m12s
verify-and-publish / publish (push) Has been skipped
Task 15d stopped on a real blocker rather than working around it: the
blocks it assembles from take plain string props, so /full-guide/ cannot
render both locales without either duplicating blocks or changing a
component interface, and both are outside page-migrator scope.

Tasks 07-11 predate the language contract task 15c wrote, which is why
none of the 19 blocks is locale-aware. This narrows the fix to the six
blocks full-guide actually uses and makes the change additive, so the
already-merged call sites that pass plain strings are unaffected.

Records that /rules/ is already fully bilingual via client-side swapping
from a content collection, and that the other five pages have no language
toggle today and must not gain one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 21:36:16 +00:00
Marcos Paulo 715f4f80b1 Merge branch 'main' into refactor/task-15d-page-full-guide 2026-09-05 21:26:03 +00:00
Marcos Paulo f7985bfe2a docs: task 15d attempt 2 needs the static Portuguese finished
Attempt 2 got the structure right and said plainly it had only done the
hero, stat and thesis regions in both locales. The remaining static prose
is the 102-entry `translations.pt` selector map in app.js, which is what
gives today's /full-guide/ its Portuguese.

Also records that the 55 `.en` reads in the selector detail panels are
correct and must not be changed: GuideSelector re-renders those per locale
on languagechange, so the server render only needs the initial locale.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 21:25:55 +00:00
Marcos Paulo 677c511979 feat: assemble astro full guide 2026-09-05 20:05:52 +00:00
Marcos Paulo 98ab6db3de docs: record why task 15d attempt 1 was rejected
verify-and-publish / gate (push) Successful in 6m14s
verify-and-publish / publish (push) Has been skipped
The attempt passed the gate and dropped Portuguese from the largest page
on a bilingual site: it scraped the legacy full-guide <main> at build
time with `?raw` and `set:html` instead of assembling the page from
the 19 block components and the content collections. That also couples
the new page to a file task 20 deletes.

Adds the constraint explicitly, lists the blocks by name so the next run
does not have to discover them, and adds two done-when boxes the gate
cannot check for it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 19:58:51 +00:00
Marcos Paulo 6d669d760a Merge branch 'refactor/task-02b-token-layer-wiring' 2026-09-05 19:57:28 +00:00
Marcos Paulo 0b4f2dd403 fix: keep the legacy :root palettes until task 20 deletes those files
Task 02b removed the `:root` palette blocks from `styles.css`,
`chapters.css`, `rules/styles.css` and `skills-review/styles.css` on the
grounds that `src/styles/tokens.css` is now the single source of truth.
That is true for the Astro pages, which import the token layer through
`BaseLayout.astro`. It is not true for the legacy pages, which are still
the live site: `index.html`, `full-guide/`, `agents/`, `models/`,
`summary/`, `rules/`, `skills/` and `skills-review/` link these
stylesheets standalone and never load `tokens.css`. Every `var(--paper)`,
`var(--ink)`, `var(--gold)` on those pages resolved to nothing.

Restores each file's own palette verbatim from main -- including the
drift (`--ink` is `#172f42` here and `#122534` there), because the
migration's contract is that the site looks exactly as it does today.
Adds `--font-sans` and `--font-mono` to each block so 02b's substitution
of those two variables for the literal font stacks keeps resolving.

Also adds `--allow-empty-input` to the stylelint lint-staged task. Since
`.stylelintignore` landed, a commit touching only legacy CSS gives
stylelint an all-ignored file list, which it treats as an error and which
made lint-staged revert this change wholesale.

The four blocks disappear with the files themselves at task 20.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 19:57:21 +00:00
Marcos Paulo be2cf2d1c5 Merge branch 'main' into refactor/task-02b-token-layer-wiring 2026-09-05 19:52:44 +00:00
Marcos Paulo 64b506aa32 refactor(tokens): make token layer authoritative and wire to layout
- Imported tokens.css directly into BaseLayout.astro.
- Removed legacy :root variable definitions from chapters.css, skills-review/styles.css, rules/styles.css, and styles.css.
- Added self-hosted --font-sans and --font-mono to tokens.css and updated legacy font stacks.
- Removed base.css.
- Added a build-output check in check-tokens.mjs to ensure the token layer is loaded in dist html files.
2026-09-05 19:31:03 +00:00
Marcos Paulo dc01460ee3 docs: tell 15d what 05b shipped and that labels are still its job
verify-and-publish / gate (push) Successful in 8m24s
verify-and-publish / publish (push) Has been skipped
2026-09-05 19:26:55 +00:00
Marcos Paulo 595006bcba Merge branch 'refactor/task-05b-guide-interactive-data' 2026-09-05 19:25:50 +00:00
Marcos Paulo 24d0af4840 Merge branch 'main' into refactor/task-05b-guide-interactive-data 2026-09-05 19:24:23 +00:00
Marcos Paulo 4b758c765d docs: add tasks 02b and 02c for the dead token layer and the gap queue
verify-and-publish / gate (push) Successful in 12m27s
verify-and-publish / publish (push) Has been skipped
2026-09-05 19:23:03 +00:00
Marcos Paulo 7f11b6e88e feat(type): self-host Manrope and DM Mono so they actually render
`styles.css` line 1 carried a malformed rule for the life of the site:

  @font-face{font-family:Manrope;src:url('https://fonts.googleapis.com/css2?...')}

`src:` in an @font-face must point at a font binary. That URL returns a CSS
stylesheet, so no browser could ever load a face from it. Every
`font-family:Manrope,Arial,sans-serif` fell through to Arial, and 'DM Mono' was
never declared as a family at all, so it fell through to generic monospace. The
intended typography has never once been seen.

Task 02 spotted this and was told to default to deleting the dead rule and
declaring the stacks that actually render. It recorded that decision, deferred
the deletion to "future component tasks", and nothing picked it up. The human
has now chosen the other branch: the real fonts.

Self-hosted rather than linked from fonts.googleapis.com because
scripts/audit-ui.mjs rejects any external <link>/<script>, and because the site
is presented in workshop rooms with unreliable networks. Latin and latin-ext
subsets only — the site is EN and PT-BR, so the cyrillic, greek and vietnamese
subsets Google also serves are dropped. Manrope ships as one variable file
covering 400-800. 89 KB total across six faces, all SIL OFL.

One public/fonts/fonts.css serves both trees, with relative url()s that each
consumer resolves against that file's own location: BaseLayout.astro links it
for Astro pages, the legacy root styles.css @imports it.

This changes how every page renders. That is the point, and it is the one
sanctioned visual change in the migration — screenshots taken before today show
Arial and are no longer a valid baseline. The three governing documents that
said "do not add a webfont" are updated so the next design-system-keeper does
not undo this.

Adds .stylelintignore, mirroring .prettierignore's legacy list for the same
reason: staging the minified styles.css to change one declaration produced ~180
declaration-block-single-line-max-declarations errors and blocked the commit.
public/fonts/fonts.css is deliberately excluded from that ignore list.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 19:07:55 +00:00
Marcos Paulo fc063f606a feat(content): migrate interactiveCopy into six typed collections
Move the six remaining bilingual datasets from app.js:160 into Astro
content collections so GuideSelector has data to drive. Mechanical copy
of 178 strings (160 localized pairs + 18 worker array strings) plus
the non-localized fields (status, path, command, score, icon, title,
number). Source field on commonSkills embedded from skillSources to
match the GuideSelectorData contract; if a URL changes, both this
entry and skillSources/<id>.json must be updated. Status kept on trees
even though GuideSelectorData omits it — index.html renders it.

Did not delete interactiveCopy from app.js: legacy page still consumes
it, and verify.mjs still asserts against it. Did not migrate the
labels (data.labels.*) — those live inside render functions in app.js
and belong to 15d.
2026-09-05 18:48:07 +00:00
Marcos Paulo 421c84ff92 Merge branch 'refactor/task-13-page-chapters'
verify-and-publish / gate (push) Successful in 3m11s
verify-and-publish / publish (push) Has been skipped
2026-09-05 18:40:36 +00:00
Marcos Paulo d62c6bf958 Merge branch 'main' into refactor/task-13-page-chapters 2026-09-05 18:40:03 +00:00
Marcos Paulo 99ccc8e249 docs: list task 05b in the plan table 2026-09-05 18:39:27 +00:00
Marcos Paulo 966dfcb926 docs: add task 05b for the unmigrated interactiveCopy datasets 2026-09-05 18:39:09 +00:00
Marcos Paulo 99d42f8fbc docs: record the 15a/15b/15c contracts in the 15d brief 2026-09-05 18:04:29 +00:00
Marcos Paulo c19e77bcac fix(chapters): narrow optional section fields in page frontmatter
The chapters schema marks section.eyebrow / panelLabel / panelCode /
steps / copy as optional, but pages /agents/, /models/, /skills/
consume them — index access without narrowing failed astro check with
ts(18048). Same for SkillPackageExplorer: aria-selected was String(bool)
which widened to plain string and failed ts(2322) against
ButtonHTMLAttributes.

Fix: guard each required field with a helper that throws a clear
message on missing data, then read .en / .map from the narrowed value.
Page rendering is unchanged — dist/ HTML for all four files is
byte-identical before and after.

No any / as any / ! / @ts-ignore. Schema and tsconfig untouched.
2026-09-05 17:41:38 +00:00
Marcos Paulo 73d1b62989 Merge branch 'main' into refactor/task-13-page-chapters 2026-09-05 17:31:14 +00:00
Marcos Paulo 8388dd63fe fix(skills): keep file-prefix and label joined by template literal
Prettier reformats JSX into one expression per line; splitting
"{file.prefix}{file.label}" across two lines inserts a literal
whitespace text node between them. Snapshot diff against
.agents/snapshots/skills.txt showed the rendered HTML emitted
"├──  SKILL.md" (two spaces) where vanilla showed one. Joining
the values into a single template expression keeps the rendered
text byte-identical to the legacy source.
2026-09-05 17:24:54 +00:00
Marcos Paulo 9621ba44bf feat: migrate chapter pages models, agents, skills to Astro
Migrate the three remaining chapter pages to Astro routes, sharing
ChapterLayout and ChapterHero/TopBar/SiteFooter blocks. /summary/
already in place from task 12.

- /models/ -> src/pages/models.astro (zero JS)
- /agents/ -> src/pages/agents.astro (zero JS)
- /skills/ -> src/pages/skills.astro (one island: SkillPackageExplorer)

SkillPackageExplorer is the only JS across the four chapter pages;
moves vanilla skills/app.js content verbatim into the island. Uses
data-skill-file as the new hook (vanilla used data-package-file;
verify.mjs still asserts that on the legacy index.html).

Copy lives in src/content/chapters/{models,agents,skills}.json. All
four pages pass empty-text snapshot diffs against
.agents/snapshots/{models,agents,skills,summary}.txt. pnpm run verify
green: verify.mjs (16 sections), audit-ui.mjs, and check-tokens.mjs
(212 marked token-gap markers, 0 unsuppressed).

Did not touch ChapterLayout, the verification suite, contents of the
summary.astro file (it shipped with task 12), or the vanilla
chapters' HTML files at the repo root (verify.mjs still reads those).
2026-09-05 17:23:38 +00:00
259 changed files with 9438 additions and 2496 deletions
+7 -5
View File
@@ -20,11 +20,13 @@ palettes and a broken `@font-face`. **Load skills**: `design-tokens`,
`--paper`, `--muted`, `--line`, `--gold` likewise. Most deltas are
sub-perceptual and can be canonicalized. `--blue` (`#527f9f` vs `#215675`) is
visibly different — screenshot both and get a human decision.
2. **The fonts have never rendered.** The `@font-face` in `styles.css:1` points
`src:` at a Google Fonts _stylesheet_, so Manrope and DM Mono have always
fallen back to Arial and generic monospace. Self-hosting them is a redesign,
not a refactor. Default: delete the dead rule, declare the stacks that
actually render. Escalate if someone wants the real fonts.
2. ~~**The fonts have never rendered.**~~ **Settled 2026-09-05 — do not
reopen.** The malformed `@font-face` was escalated and the human chose the
real fonts. Manrope and DM Mono are self-hosted in `public/fonts/`, wired
through `public/fonts/fonts.css`, which `BaseLayout.astro` links and the
legacy root `styles.css` `@import`s. **Do not delete these faces and do not
replace the stacks with `Arial`/`ui-monospace`** — that instruction is
obsolete. You may add `--font-sans` / `--font-mono` tokens pointing at them.
## You own
+4 -1
View File
@@ -1,6 +1,9 @@
---
name: motion-designer
description: Adds and audits animation — transitions, state changes, optional view transitions. Use for task 17 and any change involving movement. Do not use for static layout or styling work.
description:
Adds and audits animation — transitions, state changes, optional view
transitions. Use for task 17 and any change involving movement. Do not use for
static layout or styling work.
tools: Read, Write, Edit, Bash, Grep, Glob
---
+6 -2
View File
@@ -1,6 +1,9 @@
---
name: reviewer
description: Merge gate. Reviews a task branch diff against its brief and the project rules. Use before merging any refactor task. Never writes features or fixes findings itself.
description:
Merge gate. Reviews a task branch diff against its brief and the project
rules. Use before merging any refactor task. Never writes features or fixes
findings itself.
tools: Read, Grep, Glob, Bash
---
@@ -8,7 +11,8 @@ You are the merge gate. You read diffs and report. **You do not write features
and you do not fix what you find** — you name it precisely enough that the
owning agent can.
**Read**: the task file, then every rule in `.agents/rules/` relevant to the diff.
**Read**: the task file, then every rule in `.agents/rules/` relevant to the
diff.
## Order of checks — highest-value first
+54 -46
View File
@@ -1,44 +1,47 @@
# Context: architecture, current and target
# Context: architecture
## Current (no build step)
## Current (Astro, static output)
Ten hand-written HTML pages, each linking its own CSS and one ES module:
Ten routes, one `src/pages/` entry each, built to `dist/`:
| Route | Page | Script | Stylesheets |
| --- | --- | --- | --- |
| `/` | `index.html` | — | `chapters.css`, `landing.css` |
| `/full-guide/` | `full-guide/index.html` | `app.js` (50 KB) | `styles.css`, `responsive.css`, `audit.css` |
| `/summary/` | `summary/index.html` | — | `chapters.css` |
| `/models/` | `models/index.html` | — | `chapters.css` |
| `/agents/` | `agents/index.html` | — | `chapters.css` |
| `/skills/` | `skills/index.html` | `skills/app.js` | `skills/styles.css` |
| `/rules/` | `rules/index.html` | `rules/app.js` | `rules/styles.css` |
| `/skills-review/` | `skills-review/index.html` | `skills-review/app.js` | `skills-review/styles.css`, `change-lens.css` |
| `/hands-on/starter/` | lab fixture | own | own |
| `/hands-on/rules/` | lab fixture | own | own |
| Route | Page | Islands |
| -------------------- | ------------------------------- | ----------------------------------------------- |
| `/` | `src/pages/index.astro` | — |
| `/full-guide/` | `src/pages/full-guide.astro` | `GuideSelector`, `LanguageToggle`, `CopyPrompt` |
| `/summary/` | `src/pages/summary.astro` | — |
| `/models/` | `src/pages/models.astro` | — |
| `/agents/` | `src/pages/agents.astro` | — |
| `/skills/` | `src/pages/skills.astro` | `SkillPackageExplorer` |
| `/rules/` | `src/pages/rules.astro` | `RulesInteractive` |
| `/skills-review/` | `src/pages/skills-review.astro` | `legacy/skills-review/app.js` |
| `/hands-on/starter/` | `public/` lab fixture | own |
| `/hands-on/rules/` | `public/` lab fixture | own |
Weight is concentrated: `app.js` 50 KB, `responsive.css` 30 KB,
`skills-review/catalog.js` 27 KB, `skills-review/submitted-catalog.js` 18 KB.
## What is still unmigrated
### What each big file actually is
`legacy/` holds the parts the migration did not componentize. They are not dead
files — the pages listed above import them, and the build fails without them.
- **`app.js`** — not really application code. It is a **bilingual content
database** (`phases`, `handsOnPrompts`, `modelGuide`, `skillSources`,
`skillInstallPrompts`, each keyed `{en, pt}`) plus ~12 small `render*`
functions that swap `innerHTML` on tab clicks. ~50 `en:` keys. The content
should become data; only the tab behaviour is interactive.
- **`responsive.css`** — a 30 KB append-only layer of overrides bolted on top of
`styles.css`. Expect large parts to be dead once layout moves into components.
Do not port it verbatim.
- **`skills-review/catalog.js`** — the real data model of the review desk: one
entry per submitted skill with `id`, `author`, `title`, `status`, `focus`,
`wins[]`, `improve[]`, `extras`, `improved` (full markdown). 24 entries across
`catalog.js` + `submitted-catalog.js`. This is already a content collection in
all but name.
- **`skills-review/files.js` / `submitted-files.js`** — generated file manifests.
- **`vote.js`** — the vote widget island; talks to `vote-service/`.
- **`legacy/styles/guide.css`** (was `styles.css`) — the editorial visual
system, imported by `full-guide.astro`.
- **`legacy/styles/audit.css`** (was `full-guide/audit.css`) — responsive audit
overrides, imported by `full-guide.astro`.
- **`legacy/styles/chapters.css`** — imported by `ChapterLayout.astro`.
- **`legacy/styles/skills.css`**, **`skills-review.css`**, **`change-lens.css`**
— imported by their respective pages.
- **`legacy/skills-review/`** — `app.js` and the module graph under it
(`catalog.js`, `submitted-catalog.js`, `files.js`, `submitted-files.js`,
`vote.js`). `catalog.js` + `submitted-catalog.js` are the review desk's real
data model, 24 entries; they are a content collection in all but name.
## Target (Astro)
These sit outside `src/` deliberately: `check-tokens.mjs` sweeps `src`, and
these files are full of raw hex and unnamed breakpoints. Moving one into `src/`
means migrating it to tokens in the same change, not adding an exclusion.
`responsive.css`, `landing.css`, `app.js`, `rules/app.js`, `rules/styles.css`,
and `skills/app.js` were deleted at cutover: their content lives in components.
## Layout
```
src/
@@ -51,15 +54,15 @@ public/
hands-on/ lab fixtures copied verbatim, never processed
```
### Non-negotiables for the target
### Non-negotiables
- **URLs do not change.** `/full-guide/`, `/skills-review/`, `/hands-on/starter/`
and the rest must resolve exactly as they do now, trailing slash included.
Existing links (including `docs/`, SilverBullet, and shared URLs with
`?author=…&skill=…&view=…` query params) must keep working.
- **Zero JS by default.** Seven of the ten pages ship no JavaScript today.
They must still ship none. Islands are opt-in, per component, and justified.
- **`hands-on/` stays vanilla.** It goes in `public/` untouched. It is a lab
- **URLs do not change.** `/full-guide/`, `/skills-review/`,
`/hands-on/starter/` and the rest must resolve exactly as they do now,
trailing slash included. Existing links (including `docs/`, SilverBullet, and
shared URLs with `?author=…&skill=…&view=…` query params) must keep working.
- **Zero JS by default.** Seven of the ten pages ship no JavaScript. They must
still ship none. Islands are opt-in, per component, and justified.
- **`hands-on/` stays vanilla.** It lives in `public/` untouched. It is a lab
fixture, not a component.
- **No external runtime requests.** `audit-ui.mjs` enforces this and it is part
of the site's thesis. Self-host anything you add.
@@ -69,7 +72,12 @@ public/
## Companion service
`vote-service/` is a Go API on its own Kubernetes deploy cycle, reached by the
review desk over `window.SKILLS_REVIEW_VOTE_API`. The refactor does not touch
it. Keep the global, or replace it with a build-time `PUBLIC_VOTE_API` env var —
but if you do, update `vote-service/README.md` in the same change.
The vote API is a Go service on its own Kubernetes deploy cycle, reached by the
review desk over `window.SKILLS_REVIEW_VOTE_API`. Its source left this
repository on 2026-09-06; the deployed service is unchanged, and the review desk
still calls it. Keep the global, or replace it with a build-time
`PUBLIC_VOTE_API` env var — but if you do, update the service's own README in
the same change.
Its one-vote-per-IP assertion left `verify.mjs` with it. See
[`assertion-removals.md`](assertion-removals.md).
+26
View File
@@ -0,0 +1,26 @@
# Assertion removal ledger
`scripts/verify.mjs` may only lose an assertion by adding an entry here. The
gate counts the `## ` headings in this file and allows exactly that many
removals below the recorded floor — so a reduction is impossible without a
written reason landing in the same commit, as a visible diff.
Adding an entry is not a formality. An assertion pins a real contract; removing
one means that contract is now unverified. Say where it moved, or say plainly
that nothing checks it any more.
## vote-service one-vote-per-IP contract
**Removed:** 2026-09-06, when `vote-service/` was taken out of this repository.
**What it asserted:** that `vote-service/main.go` contained both
`X-Forwarded-For` and `one active vote per skill` — the review desk's only
anti-abuse control, one vote per visitor enforced server-side by source IP.
**Why it went:** there is no file left to read. The check was a substring match
against source that now lives elsewhere.
**Where it must be re-asserted:** in whichever repository holds the service. The
deployed service still enforces the contract; nothing in this repository proves
it. If `vote-service/` ever comes back here, restore the assertion and delete
this entry.
+47 -45
View File
@@ -8,18 +8,18 @@ files, not assumed.
The same semantic names carry different values depending on which stylesheet
loaded them:
| Token | `styles.css`, `rules/styles.css` | `chapters.css`, `skills-review/styles.css` | `hands-on/*/styles.css` |
| --- | --- | --- | --- |
| `--paper` | `#f5f4f1` | `#f6f3ed` | `#f4f3ef` |
| `--ink` | `#172f42` | `#122534` | `#173044` |
| `--muted` | `#697b89` | `#65717a` | `#687d8c` |
| `--line` | `#d8dee2` | `#d0d5d2` | `#d5dde1` |
| `--blue` | `#527f9f` | `#215675` | `#5683a1` |
| `--gold` | `#efc76b` | `#ebbf58` | `#efc86d` |
| `--accent` | `#7c78a8` | — | — |
| `--deep` | `#102536` | — | — |
| `--red` | — | `#a7483f` (chapters only) | — |
| `--violet` | — | `#6b668f` (review desk only) | — |
| Token | `styles.css`, `rules/styles.css` | `chapters.css`, `skills-review/styles.css` | `hands-on/*/styles.css` |
| ---------- | -------------------------------- | ------------------------------------------ | ----------------------- |
| `--paper` | `#f5f4f1` | `#f6f3ed` | `#f4f3ef` |
| `--ink` | `#172f42` | `#122534` | `#173044` |
| `--muted` | `#697b89` | `#65717a` | `#687d8c` |
| `--line` | `#d8dee2` | `#d0d5d2` | `#d5dde1` |
| `--blue` | `#527f9f` | `#215675` | `#5683a1` |
| `--gold` | `#efc76b` | `#ebbf58` | `#efc86d` |
| `--accent` | `#7c78a8` | — | — |
| `--deep` | `#102536` | — | — |
| `--red` | — | `#a7483f` (chapters only) | — |
| `--violet` | — | `#6b668f` (review desk only) | — |
Most deltas are a few units per channel — drift, not intent. `--blue` is the
exception: `#527f9f` vs `#215675` is a visible difference and may be deliberate.
@@ -34,35 +34,36 @@ exception: `#527f9f` vs `#215675` is a visible difference and may be deliberate.
Do not "just pick one" silently in the middle of another task. This is its own
reviewed change with visual diffs attached.
## The typography you see is not the typography that was written
## The typography — fixed 2026-09-05
`styles.css` line 1:
`styles.css` line 1 used to read:
```css
@font-face{font-family:Manrope;src:url('https://fonts.googleapis.com/css2?family=DM+Mono&family=Manrope:wght@400;600;700;800&display=swap')}
@font-face {
font-family: Manrope;
src: url('https://fonts.googleapis.com/css2?family=DM+Mono&family=Manrope:wght@400;600;700;800&display=swap');
}
```
`src:` points at a **CSS stylesheet**, not a font file. No browser can load a
font from that, so:
`src:` in an `@font-face` must point at a font binary. That URL returns a CSS
stylesheet, so no browser could load a face from it. For the whole life of the
site, every `font-family:Manrope,Arial,sans-serif` rendered as **Arial** and
every `font:… 'DM Mono',monospace` rendered as the **generic monospace** face —
`'DM Mono'` was never declared as a family at all.
- every `font-family:Manrope,Arial,sans-serif` renders as **Arial**
- every `font:… 'DM Mono',monospace` renders as the **generic monospace** face
- there are no `@font-face` blocks anywhere else and zero font files in the repo
- `scripts/audit-ui.mjs` only rejects external `<link>`/`<script>` tags, so this
slipped through the "dependency-free" audit
**This was escalated and the human chose the real fonts.** Manrope and DM Mono
are now self-hosted in `public/fonts/`, latin and latin-ext subsets only, under
the SIL Open Font License. One `fonts.css` serves both trees: Astro links it
from `BaseLayout.astro`, the legacy root `styles.css` `@import`s it. Self-hosted
rather than linked from Google because `scripts/audit-ui.mjs` rejects any
external `<link>`/`<script>`, and because the site is presented in workshop
rooms with unreliable networks.
**This is a trap for the refactor.** Self-hosting Manrope and DM Mono in Astro
is the obvious "fix" — and it would change how every page looks, violating
"maintain the same styles". Treat it as an explicit product decision:
**This changed how every page renders**, deliberately. It is the one sanctioned
visual change in the migration. Screenshots taken before 2026-09-05 show Arial
and are no longer a valid baseline.
- **Keep current rendering**: delete the dead `@font-face`, replace the font
stacks with what actually renders today (`Arial, sans-serif` /
`ui-monospace, monospace`). Zero visual change. Honest CSS.
- **Adopt the intended fonts**: self-host the woff2 files in `public/fonts/`,
add real `@font-face` with `font-display:swap`. Better-looking, but it is a
redesign and needs sign-off plus fresh screenshots.
Default to the first unless a human says otherwise.
`Georgia, serif` for emphasis (`h1 em`, `.hero em`) is untouched and still real.
## Type scale
@@ -71,13 +72,13 @@ real — it is a system font, so it does render. Keep it.
Sizes are all `clamp()`, roughly:
| Role | Value |
| --- | --- |
| Display / `h1` | `clamp(56px,9vw,126px)` |
| Section `h2` | `clamp(36px,5vw,65px)` |
| Sub-head | `clamp(24px,3vw,38px)` |
| Pull-quote | `clamp(22px,3vw,36px)` |
| Body | `15px/1.6``18px` |
| Role | Value |
| --------------- | --------------------------------------------------------- |
| Display / `h1` | `clamp(56px,9vw,126px)` |
| Section `h2` | `clamp(36px,5vw,65px)` |
| Sub-head | `clamp(24px,3vw,38px)` |
| Pull-quote | `clamp(22px,3vw,36px)` |
| Body | `15px/1.6``18px` |
| Eyebrow / label | `1011px` monospace, `letter-spacing:.08.1em`, uppercase |
There are 14+ distinct clamp triples doing near-identical jobs. Collapse to a
@@ -87,11 +88,12 @@ should be unchanged within a pixel or two at common viewports.
## Breakpoints
Sixteen distinct max-widths are in use: 420, 520, 530, 560, 600, 620, 720, 800,
850, 880, 900, 1000, 1050, 1100 — plus `min-width:1600px` and `min-width:2200px`.
850, 880, 900, 1000, 1050, 1100 — plus `min-width:1600px` and
`min-width:2200px`.
Collapse to a named set (suggested: 560 / 800 / 1100 / 1600 / 2200) and prove
equivalence with screenshots at the *old* breakpoint values, since that is
where regressions will hide.
equivalence with screenshots at the _old_ breakpoint values, since that is where
regressions will hide.
`@media(prefers-reduced-motion:reduce)` is already respected in several
stylesheets. Keep it — see [`../rules/animation.md`](../rules/animation.md).
@@ -100,8 +102,8 @@ stylesheets. Keep it — see [`../rules/animation.md`](../rules/animation.md).
The visual identity is editorial-print: flat colour blocks, hairline `1px`
rules, uppercase monospace eyebrows with wide tracking, very tight negative
letter-spacing on display type (`-.06em``-.08em`), grid layouts with `gap:1px`
over a background colour to fake borders, and near-zero border-radius.
letter-spacing on display type (`-.06em``-.08em`), grid layouts with
`gap:1px` over a background colour to fake borders, and near-zero border-radius.
That last trick (`gap:1px` + parent background) is used everywhere. It is
intentional. Do not replace it with `border`.
+2 -1
View File
@@ -49,4 +49,5 @@ likely to fail; verify before shipping.
## Bilingual content
`<html lang>` must change with the language toggle, not just the text. Screen
readers pick pronunciation from it. This already works today — do not regress it.
readers pick pronunciation from it. This already works today — do not regress
it.
+8 -4
View File
@@ -20,12 +20,16 @@ Several current stylesheets already honour it. Every new animation must:
```css
@media (prefers-reduced-motion: reduce) {
* { animation-duration: .01ms !important; animation-iteration-count: 1 !important;
transition-duration: .01ms !important; scroll-behavior: auto !important; }
* {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
```
Reduced motion means *reduced*, not *broken*: the end state must still be
Reduced motion means _reduced_, not _broken_: the end state must still be
correct and the interface still usable. Test it — in DevTools, Rendering →
Emulate `prefers-reduced-motion`.
@@ -35,7 +39,7 @@ Emulate `prefers-reduced-motion`.
Animating `width`, `height`, `top`, `left`, or `margin` forces layout on every
frame and will show up as a failed INP.
- `will-change` only on an element about to animate, removed after. Leaving it
on permanently costs memory and can *hurt* performance.
on permanently costs memory and can _hurt_ performance.
- Prefer CSS transitions. Reach for the Web Animations API only for sequencing
that CSS cannot express. Do not add an animation library — it is a runtime
dependency on a site whose thesis is having none.
+14 -11
View File
@@ -15,12 +15,12 @@ this site's ten pages ship no JS today and must continue to.
Only these need interactivity. Anything else claiming island status is wrong:
| Island | Why | Directive |
| --- | --- | --- |
| Guide phase/tab switchers | click-driven panel swap | `client:visible` |
| Review desk catalog + file viewer | search, filter, fetch source files | `client:load` |
| Vote widget | talks to `vote-service/` | `client:visible` |
| Language toggle | swaps EN/PT across the page | `client:idle` |
| Island | Why | Directive |
| --------------------------------- | ---------------------------------- | ---------------- |
| Guide phase/tab switchers | click-driven panel swap | `client:visible` |
| Review desk catalog + file viewer | search, filter, fetch source files | `client:load` |
| Vote widget | talks to the vote API | `client:visible` |
| Language toggle | swaps EN/PT across the page | `client:idle` |
## Structure
@@ -31,8 +31,11 @@ Only these need interactivity. Anything else claiming island status is wrong:
// 3. destructure Astro.props
// 4. derived values — no side effects, no fetch in components
---
<!-- markup -->
<style>/* component-scoped */</style>
<style>
/* component-scoped */
</style>
```
- Typed props always: `interface Props { … }`, then `const { … } = Astro.props`.
@@ -60,13 +63,13 @@ almost one-to-one — do that rather than importing a 27 KB JS file.
The site is served from `/ai-for-dummies/`. Set `base` in `astro.config.mjs` and
never hand-write an absolute internal path. Use `import.meta.env.BASE_URL`.
Existing routes are load-bearing and must not change, including trailing
slashes and the review desk's query params.
Existing routes are load-bearing and must not change, including trailing slashes
and the review desk's query params.
## Never
- No UI framework (React/Vue/Svelte) unless a task brief explicitly calls for it.
Astro components plus a little vanilla JS cover everything here.
- No UI framework (React/Vue/Svelte) unless a task brief explicitly calls for
it. Astro components plus a little vanilla JS cover everything here.
- No CSS framework. This site has a hand-built visual identity — see
[`theming.md`](theming.md).
- No external runtime requests. Self-host. `audit-ui.mjs` enforces it.
+3 -3
View File
@@ -3,7 +3,7 @@
## Match what is there
This codebase has a real voice: dense one-liner CSS, terse ES modules, comments
that explain *why* and never *what*. Do not reformat it into someone else's
that explain _why_ and never _what_. Do not reformat it into someone else's
house style as a side effect of a task.
The one exception is CSS minification-by-hand — `styles.css` is single-line and
@@ -44,5 +44,5 @@ overrides, and the temptation during migration will be to port it wholesale
## Commits
Present tense, lowercase, `type: subject`, matching the existing log
(`feat:`, `fix:`, `docs:`). The body explains why, and states what you did not do.
Present tense, lowercase, `type: subject`, matching the existing log (`feat:`,
`fix:`, `docs:`). The body explains why, and states what you did not do.
+2 -1
View File
@@ -3,7 +3,8 @@
## When to make a component
Extract when the same markup appears **three times**, or when a block has a name
a person would use out loud ("the eyebrow", "the route card", "the phase panel").
a person would use out loud ("the eyebrow", "the route card", "the phase
panel").
Do not extract on the second occurrence. Two similar blocks often diverge; the
premature abstraction costs more than the duplication.
+2 -2
View File
@@ -55,5 +55,5 @@ hand-rolled client-side renderer. That deletes code and improves fidelity.
Careful: `skill-reviews/improved/**/SKILL.md` is **generated** from those
entries by `scripts/build-skill-review.mjs`, and the generated files are
committed. Keep that generator working, or replace it and update every
reference to it.
committed. Keep that generator working, or replace it and update every reference
to it.
+42
View File
@@ -104,4 +104,46 @@ if (findings.length) {
findings.forEach((finding) => console.error(` ${finding}`));
process.exit(1);
}
import { existsSync } from 'node:fs';
import { basename } from 'node:path';
if (existsSync('dist')) {
const builtCss = walk('dist').filter((p) => p.endsWith('.css'));
const tokensBuilt = builtCss.find((p) => /[\\/]tokens\.[^\\/]+\.css$/.test(p));
if (!tokensBuilt) {
console.error('token check failed — tokens.css was not built into dist/');
process.exit(1);
}
const tokensContent = readFileSync(tokensBuilt, 'utf8');
if (!tokensContent.includes('#527f9f')) {
console.error(
'token check failed — built tokens.css does not contain the canonical --blue value #527f9f',
);
process.exit(1);
}
const htmlFiles = walk('dist').filter(
(p) =>
p.endsWith('.html') &&
!p.includes('/hands-on/') &&
!p.includes('\\hands-on\\') &&
!p.includes('/submitted-skills/') &&
!p.includes('\\submitted-skills\\'),
);
const tokenChunkName = basename(tokensBuilt);
for (const html of htmlFiles) {
const content = readFileSync(html, 'utf8');
if (!content.includes(tokenChunkName)) {
console.error(
`token check failed — ${html} does not load the token layer (${tokenChunkName})`,
);
process.exit(1);
}
}
}
console.log('token check passed');
+173
View File
@@ -0,0 +1,173 @@
#!/usr/bin/env node
// Compare the *computed* styles of a legacy page against its Astro
// replacement, at several viewport widths.
//
// node .agents/scripts/computed-style-diff.mjs full-guide
// node .agents/scripts/computed-style-diff.mjs full-guide --widths 560,880,1050
//
// Why this exists: a ported media query can sit in the built stylesheet,
// match the viewport, and still do nothing. Astro scopes a component's rules
// as `.tree-node[data-astro-cid-lsutp3lb]` (specificity 0,2,0); a rule ported
// verbatim as `.tree-node` (0,1,0) loses to it and never applies. Task 15e
// attempt 4 shipped exactly that: `@media (max-width: 1050px) .tree-node
// { width: 145px }` was present in dist and the node stayed 180px wide.
//
// Checking that the breakpoint *appears* in the built CSS cannot catch this.
// Only asking the browser what it actually computed can.
import { spawn } from 'node:child_process';
import { cpSync, mkdtempSync, readFileSync, rmSync } from 'node:fs';
import { createServer } from 'node:net';
import { tmpdir } from 'node:os';
import { join } from 'node:path';
import { chromium } from 'playwright';
const route = process.argv[2];
if (!route) {
console.error('usage: computed-style-diff.mjs <route> [--widths a,b,c]');
process.exit(2);
}
const widthsArg = process.argv.indexOf('--widths');
const widths =
widthsArg === -1
? [520, 560, 600, 620, 720, 800, 880, 1050, 1100, 1600]
: process.argv[widthsArg + 1].split(',').map(Number);
// The selectors worth checking are the ones the responsive layer moves at a
// breakpoint, so read them out of the legacy stylesheet's @media blocks only.
// Taking every class in the file buries the signal under generic ones like
// `.active`, whose state the islands own anyway.
const responsive = readFileSync(new URL('../../responsive.css', import.meta.url), 'utf8');
const mediaBlocks = [];
for (const match of responsive.matchAll(/@media[^{]*\{/g)) {
let depth = 0;
for (let i = match.index; i < responsive.length; i += 1) {
if (responsive[i] === '{') depth += 1;
else if (responsive[i] === '}') {
depth -= 1;
if (depth === 0) {
mediaBlocks.push(responsive.slice(match.index + match[0].length, i));
break;
}
}
}
}
const selectors = [...new Set(mediaBlocks.join('\n').match(/\.[a-z][a-z0-9-]*/g) || [])].sort();
// Properties a responsive rule actually moves. Comparing every property would
// drown the signal in font stacks and inherited colour.
const PROPERTIES = [
'display',
'grid-template-columns',
'grid-template-rows',
'flex-direction',
'width',
'height',
'max-width',
'padding',
'margin',
'gap',
'font-size',
'position',
'inset',
'overflow',
];
// The legacy pages were deleted at cutover; run this from a pre-cutover
// worktree, or the legacy side will 404.
const legacyPath = route === 'index' ? 'index.html' : `${route}/index.html`;
const astroPath = route === 'index' ? '' : `${route}/`;
const staging = mkdtempSync(join(tmpdir(), 'af-csd-'));
cpSync('dist', join(staging, 'ai-for-dummies'), { recursive: true });
const freePort = () =>
new Promise((resolve, reject) => {
const probe = createServer();
probe.on('error', reject);
probe.listen(0, '127.0.0.1', () => {
const { port } = probe.address();
probe.close(() => resolve(port));
});
});
const legacyPort = await freePort();
const astroPort = await freePort();
const serve = (dir, port) =>
spawn('python3', ['-m', 'http.server', String(port), '-d', dir], { stdio: 'ignore' });
const servers = [serve('.', legacyPort), serve(staging, astroPort)];
const stop = () => {
servers.forEach((s) => s.kill());
rmSync(staging, { recursive: true, force: true });
};
// Every element matching each selector, so a rule that applies to the first
// node and not the rest cannot pass.
const collect = ([selectors, properties]) => {
const out = {};
for (const selector of selectors) {
const nodes = [...document.querySelectorAll(selector)];
out[selector] = nodes.map((node) => {
const style = getComputedStyle(node);
return properties
.map((property) => `${property}:${style.getPropertyValue(property)}`)
.join(';');
});
}
return out;
};
let failures = 0;
try {
const browser = await chromium.launch();
const read = async (url, width) => {
const page = await browser.newPage({ viewport: { width, height: 900 } });
const response = await page.goto(url, { waitUntil: 'load' });
if (!response || !response.ok()) {
throw new Error(`${url} returned ${response ? response.status() : 'no response'}`);
}
await page.waitForTimeout(1500);
const styles = await page.evaluate(collect, [selectors, PROPERTIES]);
await page.close();
return styles;
};
for (const width of widths) {
const legacy = await read(`http://localhost:${legacyPort}/${legacyPath}`, width);
const astro = await read(`http://localhost:${astroPort}/ai-for-dummies/${astroPath}`, width);
for (const selector of selectors) {
const before = legacy[selector];
const after = astro[selector];
if (before.length === 0 && after.length === 0) continue;
if (before.length !== after.length) {
console.log(
`${width}px ${selector} legacy ${before.length} nodes, astro ${after.length}`,
);
failures += 1;
continue;
}
let reported = 0;
before.forEach((expected, index) => {
if (expected === after[index]) return;
failures += 1;
// Three examples is enough to identify a rule that did not apply.
reported += 1;
if (reported > 3) return;
const differing = expected
.split(';')
.filter((pair, i) => pair !== after[index].split(';')[i]);
const got = after[index].split(';').filter((pair, i) => pair !== expected.split(';')[i]);
console.log(`${width}px ${selector}[${index}]`);
console.log(` legacy ${differing.join(' ')}`);
console.log(` astro ${got.join(' ')}`);
});
}
}
await browser.close();
console.log(failures === 0 ? 'computed styles match' : `${failures} computed-style differences`);
process.exitCode = failures === 0 ? 0 : 1;
} finally {
stop();
}
+26 -2
View File
@@ -43,7 +43,20 @@ step "types"
pnpm exec astro check
step "build"
pnpm run build
# `astro build` exits 0 even when vite fails to resolve an asset: the cutover
# left a stale `@import` in a moved stylesheet and every gate stayed green for
# it. Treat a logged error as a failed build.
build_log=$(mktemp)
if ! pnpm run build 2>&1 | tee "$build_log"; then
rm -f "$build_log"
exit 1
fi
if grep -q '\[ERROR\]' "$build_log"; then
echo "gate: astro build logged an error and still exited 0. See above." >&2
rm -f "$build_log"
exit 1
fi
rm -f "$build_log"
step "content contracts"
pnpm run verify
@@ -51,8 +64,19 @@ pnpm run verify
# The assertion count is the thing agents are most tempted to "fix" downward.
# Compare against origin/main and refuse a silent reduction.
step "assertion coverage"
# Task 19 restored the 42 legacy facts and added ten output snapshots: 84 is the
# floor, in addition to whatever origin/main currently requires.
#
# A removal is allowed only by writing a reason into the ledger. The gate counts
# its entries and lowers the bar by exactly that many, so the bar cannot move
# without a visible diff explaining why. Deleting an entry to buy headroom is
# the same offence as deleting the assertion was.
ledger=.agents/context/assertion-removals.md
current=$(grep -c 'throw new Error' scripts/verify.mjs)
baseline=$(git show origin/main:scripts/verify.mjs 2>/dev/null | grep -c 'throw new Error' || echo "$current")
allowed=$(grep -c '^## ' "$ledger" 2>/dev/null || echo 0)
baseline=$(git show origin/main:scripts/verify.mjs 2>/dev/null | grep -c 'throw new Error' || echo 0)
if [ "$baseline" -lt 84 ]; then baseline=84; fi
baseline=$((baseline - allowed))
if [ "$current" -lt "$baseline" ]; then
echo "gate: verify.mjs coverage fell from $baseline to $current assertions." >&2
echo " Only verification-engineer may reduce it, with a reason per removal." >&2
+123
View File
@@ -0,0 +1,123 @@
#!/usr/bin/env bash
# Build the site and publish it to the `pages` branch.
#
# .agents/scripts/publish-pages.sh # publish
# .agents/scripts/publish-pages.sh --dry-run # build and report, push nothing
# .agents/scripts/publish-pages.sh --pending X # main is *about* to become X
#
# `--pending` exists for the pre-push hook. Git has no post-push hook, so the
# hook necessarily runs before main lands on the remote and the usual "HEAD must
# equal origin/main" check cannot hold yet. The caller asserts the SHA the push
# will create, and the hook only asserts it after confirming the push is a
# fast-forward.
#
# `pages` is what the Gitea Pages Server actually serves. Publishing overwrites
# the live site. There is no staging environment between here and visitors.
#
# This never checks `pages` out. It writes a tree straight from `dist/` with
# plumbing (`write-tree` + `commit-tree`), so your working tree is untouched and
# a failure halfway through leaves nothing behind. The commit is parented on the
# current `pages`, so the branch keeps its history and rollback is one push.
set -euo pipefail
cd "$(git rev-parse --show-toplevel)"
dry_run=0
pending=''
while [ $# -gt 0 ]; do
case "$1" in
--dry-run) dry_run=1 ;;
--pending)
shift
pending="${1:-}"
;;
*)
echo "publish-pages: unknown argument '$1'" >&2
exit 2
;;
esac
shift
done
fail() {
echo "publish-pages: $1" >&2
exit 1
}
# Publishing a build made from uncommitted work means the live site shows
# something no commit describes, and nobody can reproduce it later.
[ -z "$(git status --porcelain)" ] || fail 'working tree is dirty; commit or stash first'
branch=$(git rev-parse --abbrev-ref HEAD)
[ "$branch" = 'main' ] || fail "publishing from '$branch'; only main is publishable"
git fetch --quiet origin pages
head=$(git rev-parse HEAD)
if [ -n "$pending" ]; then
[ "$head" = "$(git rev-parse "$pending")" ] ||
fail "HEAD is $head but the pending push is $pending"
else
git fetch --quiet origin main
[ "$head" = "$(git rev-parse origin/main)" ] ||
fail 'HEAD is not origin/main; push main first so the site matches a pushed commit'
fi
previous=$(git rev-parse origin/pages)
echo "publish-pages: building $head"
# `astro build` exits 0 even when vite fails to resolve an asset, so the exit
# code alone is not enough to know the build is whole. The gate greps for this
# too; repeat it here because this script is also run by hand.
build_log=$(mktemp)
trap 'rm -f "$build_log"' EXIT
pnpm run build >"$build_log" 2>&1 || {
cat "$build_log" >&2
fail 'astro build failed'
}
if grep -q '\[ERROR\]' "$build_log"; then
cat "$build_log" >&2
fail 'astro build logged an error and still exited 0; refusing to publish'
fi
# A build can succeed and still emit a stub -- that is exactly how this site
# would go down. Check the routes exist before overwriting anything live.
for route in index full-guide/index summary/index models/index agents/index \
skills/index rules/index skills-review/index \
hands-on/starter/index hands-on/rules/index; do
[ -s "dist/$route.html" ] || fail "dist/$route.html missing or empty; refusing to publish"
done
# GIT_INDEX_FILE must name a path that does not exist yet: git reads an existing
# empty file as a truncated index and dies with "index file smaller than
# expected". mktemp -d gives a private directory to put that path in.
index_dir=$(mktemp -d)
index="$index_dir/index"
trap 'rm -rf "$index_dir"; rm -f "$build_log"' EXIT
# `--force` because the repository .gitignore lists `dist`; here `dist` *is* the
# work tree, so those rules would otherwise exclude everything we mean to ship.
GIT_INDEX_FILE="$index" git --work-tree=dist add --all --force .
tree=$(GIT_INDEX_FILE="$index" git write-tree)
if [ "$tree" = "$(git rev-parse "$previous^{tree}")" ]; then
echo "publish-pages: dist is identical to the published tree; nothing to do"
exit 0
fi
subject="chore: publish $(git rev-parse --short "$head")"
commit=$(git commit-tree "$tree" -p "$previous" -m "$subject
Built from main $head
$(git log -1 --format=%s "$head")")
if [ "$dry_run" -eq 1 ]; then
echo "publish-pages: would push $commit to pages (previous $previous)"
echo "publish-pages: dry run, nothing pushed"
exit 0
fi
echo "publish-pages: rollback point is $previous"
echo " git push --force origin $previous:refs/heads/pages"
# AF_PUBLISHING stops the pre-push hook recursing into this script.
AF_PUBLISHING=1 git push --force origin "$commit:refs/heads/pages"
echo "publish-pages: published $commit"
+185
View File
@@ -0,0 +1,185 @@
#!/usr/bin/env node
// Compare the *rendered* text of a legacy page against its Astro replacement.
//
// node .agents/scripts/rendered-text-diff.mjs full-guide
// node .agents/scripts/rendered-text-diff.mjs full-guide --pt
//
// Why this exists: scripts/verify.mjs reads the legacy files, so a migrated
// page can drop half its content and still pass the gate. Task 15d shipped
// /full-guide/ missing 86 rendered spans -- the entire verification section,
// the hands-on exercise brief, and both "Clone from Gitea" links -- and every
// check was green.
//
// Static HTML comparison is useless here: the guide's tab panels are injected
// by an island at runtime, so half the legacy page's markup has no static
// counterpart. This walks the live DOM instead and skips anything the browser
// is not painting -- which also drops the hidden Portuguese half of each
// bilingual pair, so the two sides line up.
//
// Requires playwright (devDependency) and two static servers; it starts both.
//
// The legacy pages were deleted at cutover, so this needs a pre-cutover tree:
// git worktree add /tmp/vanilla <pre-cutover-sha>
// and run from there, or run it from a checkout that still has them.
import { spawn } from 'node:child_process';
import { cpSync, mkdtempSync, rmSync } from 'node:fs';
import { tmpdir } from 'node:os';
import { join } from 'node:path';
import { createServer } from 'node:net';
import { chromium } from 'playwright';
// `index` is the landing page: it lives at the repository root, not in a
// directory of its own, so it needs a different path on the legacy side.
const route = process.argv[2];
if (!route) {
console.error('usage: rendered-text-diff.mjs <route> [--pt] e.g. full-guide, or index');
process.exit(2);
}
// `--pt` clicks the language toggle on both pages first. English parity is
// only half the contract: a page can render every English string and still
// leave a restored block untranslated, because the Portuguese half is a
// separate set of nodes. Only /full-guide/ and /rules/ have a toggle.
const portuguese = process.argv.includes('--pt');
const legacyPath = route === 'index' ? 'index.html' : `${route}/index.html`;
const astroPath = route === 'index' ? '' : `${route}/`;
// The built site expects to be served under the configured base path.
const staging = mkdtempSync(join(tmpdir(), 'af-rtd-'));
cpSync('dist', join(staging, 'ai-for-dummies'), { recursive: true });
// Ask the kernel for a free port rather than pinning one. Back-to-back runs
// used to collide: the previous run's server was still holding the fixed port
// while its staging directory had already been deleted, so every page came
// back as a 404 and the diff reported the whole route missing.
const freePort = () =>
new Promise((resolve, reject) => {
const probe = createServer();
probe.on('error', reject);
probe.listen(0, '127.0.0.1', () => {
const { port } = probe.address();
probe.close(() => resolve(port));
});
});
const legacyPort = await freePort();
const astroPort = await freePort();
const serve = (dir, port) =>
spawn('python3', ['-m', 'http.server', String(port), '-d', dir], { stdio: 'ignore' });
const servers = [serve('.', legacyPort), serve(staging, astroPort)];
const stop = () => {
servers.forEach((s) => s.kill());
rmSync(staging, { recursive: true, force: true });
};
// Visible text nodes, in document order, whitespace collapsed.
const visibleText = () => {
const out = [];
const walk = (node) => {
for (const child of node.childNodes) {
if (child.nodeType === Node.TEXT_NODE) {
const text = child.textContent.replace(/\s+/g, ' ').trim();
if (text) out.push(text);
continue;
}
if (child.nodeType !== Node.ELEMENT_NODE) continue;
if (child.tagName === 'SCRIPT' || child.tagName === 'STYLE') continue;
const style = getComputedStyle(child);
if (child.hidden || style.display === 'none' || style.visibility === 'hidden') continue;
walk(child);
}
};
walk(document.body);
return out;
};
try {
await new Promise((r) => setTimeout(r, 1500));
const browser = await chromium.launch();
const grab = async (url) => {
const page = await browser.newPage({ viewport: { width: 1400, height: 1000 } });
const response = await page.goto(url, { waitUntil: 'load' });
// A 404 renders as four spans of python's error page and the diff then
// reports the entire route as missing, which reads exactly like a real
// regression. Fail loudly instead.
if (!response || !response.ok()) {
throw new Error(`${url} returned ${response ? response.status() : 'no response'}`);
}
// The islands hydrate and render their initial panel on load; without this
// every panel's copy reads as missing.
await page.waitForTimeout(1200);
if (portuguese) {
const toggle = await page.$('[data-lang="pt"]');
if (!toggle) throw new Error(`no language toggle on ${url}`);
await toggle.click();
await page.waitForTimeout(1200);
}
// Islands hydrate at their own pace, and the language toggle repaints in
// more than one frame. A single read after a fixed wait is flaky, so read
// until two consecutive reads agree.
let spans = await page.evaluate(visibleText);
for (let i = 0; i < 10; i += 1) {
await page.waitForTimeout(300);
const next = await page.evaluate(visibleText);
if (next.length === spans.length && next.every((span, j) => span === spans[j])) {
spans = next;
break;
}
spans = next;
}
await page.close();
return spans;
};
const legacy = await grab(`http://localhost:${legacyPort}/${legacyPath}`);
const astro = await grab(`http://localhost:${astroPort}/ai-for-dummies/${astroPath}`);
await browser.close();
// Count occurrences, not membership. A set comparison reports zero when a
// string the legacy page paints four times is painted three times here --
// exactly the kind of near-miss that got past the earlier checks.
const tally = (spans) => {
const counts = new Map();
for (const span of spans) counts.set(span, (counts.get(span) || 0) + 1);
return counts;
};
const legacyCounts = tally(legacy);
const astroCounts = tally(astro);
const missing = [];
for (const [span, count] of legacyCounts) {
const short = count - (astroCounts.get(span) || 0);
for (let i = 0; i < short; i += 1) missing.push(span);
}
// Both directions. A string the Astro page paints and the legacy page does
// not is just as wrong: it means a translation was invented, or an English
// string was left standing where the legacy page swaps it.
const extra = [];
for (const [span, count] of astroCounts) {
const over = count - (legacyCounts.get(span) || 0);
for (let i = 0; i < over; i += 1) extra.push(span);
}
// Order counts too. Both pages can paint the same strings while a block
// sits in the wrong place -- the Portuguese eyebrow, or a reordered card
// deck -- and a count-only comparison calls that clean.
const firstOutOfOrder = legacy.findIndex((span, i) => astro[i] !== span);
const mode = portuguese ? 'pt' : 'en';
console.log(
`${mode} · legacy ${legacy.length} spans · astro ${astro.length} spans · missing ${missing.length} · extra ${extra.length}`,
);
for (const span of missing) console.log(` - ${span}`);
for (const span of extra) console.log(` + ${span}`);
if (firstOutOfOrder !== -1) {
console.log(` order diverges at span ${firstOutOfOrder}`);
console.log(` legacy: ${legacy[firstOutOfOrder]}`);
console.log(` astro: ${astro[firstOutOfOrder]}`);
}
process.exitCode = missing.length === 0 && extra.length === 0 && firstOutOfOrder === -1 ? 0 : 1;
} finally {
stop();
}
+6 -2
View File
@@ -27,8 +27,12 @@ const text = html
.replace(/<style[\s\S]*?<\/style>/gi, '')
.replace(/<!--[\s\S]*?-->/g, '')
.replace(/<[^>]+>/g, '\n')
.replace(/&amp;/g, '&').replace(/&lt;/g, '<').replace(/&gt;/g, '>')
.replace(/&quot;/g, '"').replace(/&#0?39;/g, "'").replace(/&nbsp;/g, ' ')
.replace(/&amp;/g, '&')
.replace(/&lt;/g, '<')
.replace(/&gt;/g, '>')
.replace(/&quot;/g, '"')
.replace(/&#0?39;/g, "'")
.replace(/&nbsp;/g, ' ')
.split('\n')
.map((line) => line.trim())
.filter(Boolean)
+5 -1
View File
@@ -12,8 +12,12 @@ description:
The snapshot is the only objective evidence that no content was lost.
The vanilla site was deleted at cutover. To compare against it, check the
pre-cutover tree out into a scratch worktree first:
```bash
pnpm run serve & # vanilla site on :4173
git worktree add /tmp/vanilla <pre-cutover-sha>
(cd /tmp/vanilla && python3 -m http.server 4173) &
node .agents/scripts/snapshot-route.mjs http://localhost:4173/models/ \
> .agents/snapshots/models.txt
```
+6 -3
View File
@@ -1,6 +1,9 @@
---
name: content-migration
description: Move bilingual copy out of app.js and catalog.js into typed Astro content collections without losing or altering a single string. Use for any task that relocates user-visible text.
description:
Move bilingual copy out of app.js and catalog.js into typed Astro content
collections without losing or altering a single string. Use for any task that
relocates user-visible text.
---
# Content migration
@@ -9,8 +12,8 @@ description: Move bilingual copy out of app.js and catalog.js into typed Astro c
- `app.js` — ~50 `{ en, pt }` keys across `phases`, `handsOnPrompts`,
`modelGuide`, `skillSources`, `skillInstallPrompts`
- `skills-review/catalog.js` + `submitted-catalog.js` — 24 entries with
`id`, `author`, `title`, `status`, `focus`, `wins[]`, `improve[]`, `extras`,
- `skills-review/catalog.js` + `submitted-catalog.js` — 24 entries with `id`,
`author`, `title`, `status`, `focus`, `wins[]`, `improve[]`, `extras`,
`improved` (full markdown)
These are hand-written translations with deliberate tone. **Copy them. Never
+4 -2
View File
@@ -21,8 +21,10 @@ a bug.
```bash
python3 - <<'PY'
import re
files=['styles.css','chapters.css','landing.css','rules/styles.css','skills/styles.css',
'skills-review/styles.css','hands-on/starter/styles.css','hands-on/rules/styles.css']
files=['legacy/styles/guide.css','legacy/styles/chapters.css','legacy/styles/skills.css',
'legacy/styles/skills-review.css','legacy/styles/change-lens.css',
'legacy/styles/audit.css','public/hands-on/starter/styles.css',
'public/hands-on/rules/styles.css']
seen={}
for f in files:
for m in re.finditer(r'--([a-z-]+):\s*([^;}]+)', open(f).read()):
+20 -9
View File
@@ -1,6 +1,9 @@
---
name: motion
description: Add or review animation on the ai-for-dummies site — transitions, state changes, view transitions. Use when any element moves, fades, or transforms, or when auditing existing motion for performance and reduced-motion support.
description:
Add or review animation on the ai-for-dummies site — transitions, state
changes, view transitions. Use when any element moves, fades, or transforms,
or when auditing existing motion for performance and reduced-motion support.
---
# Motion
@@ -22,10 +25,14 @@ If there is no answer, ship it static. That is a legitimate, common outcome.
```css
.panel {
transition: opacity 180ms cubic-bezier(.2,0,0,1),
transform 180ms cubic-bezier(.2,0,0,1);
transition:
opacity 180ms cubic-bezier(0.2, 0, 0, 1),
transform 180ms cubic-bezier(0.2, 0, 0, 1);
}
.panel[data-state='entering'] {
opacity: 0;
transform: translateY(6px);
}
.panel[data-state='entering'] { opacity: 0; transform: translateY(6px); }
```
- **`transform` and `opacity` only.** Animating `width`/`height`/`top`/`left`
@@ -39,14 +46,18 @@ If there is no answer, ship it static. That is a legitimate, common outcome.
```css
@media (prefers-reduced-motion: reduce) {
* { animation-duration: .01ms !important; animation-iteration-count: 1 !important;
transition-duration: .01ms !important; scroll-behavior: auto !important; }
* {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
```
Then **test it**: DevTools → Rendering → Emulate `prefers-reduced-motion:
reduce`. The end state must still be correct and the UI still usable. Reduced,
not broken.
Then **test it**: DevTools → Rendering → Emulate
`prefers-reduced-motion: reduce`. The end state must still be correct and the UI
still usable. Reduced, not broken.
## Page transitions
+13 -10
View File
@@ -1,6 +1,9 @@
---
name: verify-contract
description: Evolve scripts/verify.mjs across the Astro migration without losing coverage. Use whenever a verify assertion fails because of a refactor, or when adding checks for new architecture.
description:
Evolve scripts/verify.mjs across the Astro migration without losing coverage.
Use whenever a verify assertion fails because of a refactor, or when adding
checks for new architecture.
---
# The verification contract
@@ -29,13 +32,13 @@ report. Nobody else may reduce coverage.
## Translating assertions
| Kind | Old | New |
| --- | --- | --- |
| Content presence | `html.includes('data-phase="plan"')` | same token, read from `dist/full-guide/index.html` |
| Implementation detail | `js.includes('renderTree')` | assert the rendered output has the tree UI, not that a function is named that |
| Asset version | `'app.js?v=20260904-vote-widget'` | assert the built HTML references a hashed asset |
| Kind | Old | New |
| --------------------- | ------------------------------------ | ----------------------------------------------------------------------------- |
| Content presence | `html.includes('data-phase="plan"')` | same token, read from `dist/full-guide/index.html` |
| Implementation detail | `js.includes('renderTree')` | assert the rendered output has the tree UI, not that a function is named that |
| Asset version | `'app.js?v=20260904-vote-widget'` | assert the built HTML references a hashed asset |
Implementation-detail assertions are the dangerous ones: they *look* deletable.
Implementation-detail assertions are the dangerous ones: they _look_ deletable.
They are pinning a feature. Replace with an output-level assertion of the same
feature; never drop.
@@ -54,9 +57,9 @@ Commit the snapshots. They are the migration's regression net.
## Extend audit-ui.mjs
It rejects external `<script>`/`<link>` but **misses external URLs inside CSS**
which is exactly how the broken Google Fonts `@font-face` in `styles.css:1` got
into a "dependency-free" site. Add:
It rejects external `<script>`/`<link>` but **misses external URLs inside CSS**
which is exactly how the broken Google Fonts `@font-face` in `styles.css:1`
got into a "dependency-free" site. Add:
```js
if (/@import|src:\s*url\(['"]?https?:|url\(['"]?https?:/i.test(css))
+3 -2
View File
@@ -33,8 +33,9 @@ with sync_playwright() as p:
browser.close()
```
Run once against the vanilla site (`pnpm run serve`), once against
`pnpm run preview`. Keep both sets.
Run once against `pnpm run preview`. To compare against the vanilla site, serve
a pre-cutover worktree on :4173 first — those files are no longer on `main`.
Keep both sets.
## Compare
Binary file not shown.

Before

Width:  |  Height:  |  Size: 130 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 142 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.0 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 107 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 118 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 115 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 137 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 155 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 127 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 377 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 444 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 341 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 342 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 162 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 174 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 140 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 147 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 465 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 485 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 438 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 458 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 99 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 130 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 142 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.0 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 107 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 118 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 115 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 137 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 155 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 127 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 377 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 444 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 341 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 342 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 169 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 187 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 147 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 151 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 465 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 485 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 438 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 458 KiB

Some files were not shown because too many files have changed in this diff Show More