There was an error while loading. Please reload this page.
Add generic 'Designing Vibe Tests' playbook + link from hub
vibe-test: scores 2026-07-21
Doc Reviewer: add check 18, CLI config & integration doc drift Add a names-in-sync audit that compares the astryx.config and astryx.integration Zod schemas (packages/cli/src/lib/config-schema.mjs, the runtime source of truth) against the CLI README's field tables, so a schema field add/remove/rename that leaves the README stale is caught nightly. Includes a detection-only audit script and updates the Findings template and State JSON with a configDocDrift counter.
Doc Reviewer: document reference-doc overlay contract (id-anchored, prose-only blocks) Reference docs (astryx docs <topic> --lang zh|dense) use ReferenceTranslationDoc via api/docs.mjs, which is a separate system from the component/hook overlays already covered. Overlays now anchor by section title + block id and are prose-only; the old positional content array is rejected by the gate (docOverlays.test.mjs). Documents the shape so the Doc Reviewer generates it. Co-authored-by: Cursor <cursoragent@cursor.com>
vibe-test: scores 2026-07-20
vibe-test: scores 2026-07-19
vibe-test: scores 2026-07-18
vibe-test: scores 2026-07-17
Figma Librarian: release-gated rewrite; move operational detail out of wiki Rework the Figma Librarian role around stable dot releases instead of per-commit code diffs: gate on a new published core version, read the release notes, categorize Figma implications (incl. block examples), checkpoint, then execute staged edits (never publish). Trim the page to the general approach only — Figma file key, MCP node, API endpoints, state paths, and notification channel now live in the private automation, not on the public wiki. Fix stale references (repo URL, component naming, removed icon library).
vibe-test: scores 2026-07-15
Updated Design Conventions (markdown)
vibe-test: scores 2026-07-14
Doc Reviewer check 1: fix dead post-rebrand glob (Astryx*.tsx matched 0 files) Check 1 (Storybook @example compat) scanned 'packages/core/src/*/Astryx*.tsx'. Components were unprefixed in the Astryx rebrand, so that glob matches ZERO files and the entire check has been silently passing on nothing every run. It masked 15 real violations on main: 6 files with the Storybook-breaking ```tsx language tag plus 9 with // comments, blank lines, or a bare > inside @example code fences (all of which break autodocs rendering). Scan bare-named .tsx recursively under BOTH packages/core/src and packages/lab/src (excluding *.test.*, *.story*, *Context*) in the prose scan, the grep helper, and the python audit script. Verified the corrected scan finds the 15 files on current main.
deadcode: add CLI dynamic-registry and doc-variant entry patterns to knip config The CLI lazy-loads command modules via a data-driven registry in src/index.mjs (await import(cmd.path)), and resolves localized/dense doc variants at runtime via path.join(dir, base + '.doc.' + locale + '.mjs'). Static analysis cannot follow either, so command .mjs files and .doc.dense.mjs/.doc.zh.mjs files were reported as unused. Mark them as entry points so the detector stops flagging these false positives.
Design Conventions: refine State Representations visuals - Add Hovered (Ring style) row for field hover (emphasized border + inset ring) - Show a selected radio in the Filled-style example - Use a basic stepper (no error states) for the Edge-style example - Drop the checkbox-list image from the Depressed-style row - Split Loading (skeleton) from Processing (spinner); add an input-with-spinner example - Muted status: use a warning banner + destructive button (both carry the muted colored background) - Inverted status: show only positive/negative badges - Give agent states the shared Visuals/Representation columns, left blank
Design Conventions: content-first restructure - Condense intro into a concise marker-usage table (objective/assisted/judgment + who verifies) - Move audit mechanics (lens, check IDs, output contract) out to the Component Auditor; keep this page content-first - Reformat Design Foundations: standalone 'Why it matters' lead-in, then a header-less table of Principle / Smells / Got it right - Add a compact 'What's checkable, and where it's checked' pointer table
vibe-test: scores 2026-07-13
Dead Code role: ship detector tooling in wiki repo Move the knip tooling into tools/deadcode/ in the wiki so it travels with the instructions the Night Watch clones each run. Avoids any cross-node file transfer and keeps it version-controlled alongside the checklist. node_modules is gitignored and installed on first use via bootstrap.sh. Updates the role page tooling paths accordingly.
Add Night Watch Dead Code role New role for detecting and removing unused files, exports, types, and devDependencies via knip. Assigned to cixzhang, auto-PR mode. The detector runs out-of-repo (knip binary, config, and runner live in the operator's workspace) so nothing is added to the public repo's toolchain. Config is public-API safe: it reads each package's exports and bin as entry points and ignores CLI templates and vibe-test baselines. Scope explicitly excludes runtime dependencies (Dependencies + Quartermaster), apps/* deletions, and component conventions (Component Auditor). Updates the Roles table, role details, coordination schedule, and Home page links.
vibe-test: scores 2026-07-12
Refine rest-forwarding guidance: per-category precedence (combine/compose/clobber) + composeEventHandlers Correct the earlier oversimplified 'spread ...rest' rule. Document that prop collisions resolve per category: className/style combine (mergeProps), contract props let the component win (set after {...rest}), owned handlers compose (composeEventHandlers, #3863), neutral pass-throughs forward. Update the Component Auditor check to match — it's a judgment check on collision handling, not just 'does ...rest exist'.
Revert "Release process: advance latest branch to the release commit in post-release" This reverts commit 20347a4ead94b1d5dca01f7ea6087bb1f3275170.
Release process: advance latest branch to the release commit in post-release
Component Auditor: catch components that extend BaseProps but never forward ...rest Add a check (and the underlying API convention) for the silent-drop bug fixed in #3738 and #3852: a component extends BaseProps so data-testid/aria-* type-check, but never captures/spreads ...rest, so those pass-through attributes never reach the DOM. Documents the placement rule (after mergeProps, before component-owned role/aria) and distinguishes it from the composed-component overwrite check.
vibe-test: scores 2026-07-11
Updated Blog Review Rubric (markdown)
docs: add Blog Review Rubric wiki page
docs: document lab→core and hidden→visible template promotion gates
vibe-test: scores 2026-07-10