@adia-ai/adia-ui-forge 0.1.3 → 0.8.0

package/skills/adia-ui-release/scripts/make-ledger.mjs

@@ -1,200 +0,0 @@
-#!/usr/bin/env node
-// make-ledger.mjs — author .brain/audit-history/YYYY-MM-DD-release-vX.Y.Z.json
-// from git state + cycle-specific notes.
-//
-// Reads:
-//   - the current git HEAD (release_commit + tag_commit if same)
-//   - the 10 tags for the given version (collected from `git tag`)
-//   - the recent gate-run output (passed via --verification-file or
-//     --verification-json or computed best-effort from `npm run check:lockstep`)
-//
-// Writes:
-//   - .brain/audit-history/YYYY-MM-DD-release-vX.Y.Z.json
-//
-// Usage:
-//   node make-ledger.mjs --version 0.6.22 --date 2026-05-22 \
-//     --summary "9-package lockstep PATCH cut. Substantive: ..." \
-//     --kind release-cut
-//   node make-ledger.mjs --version 0.6.22 --date 2026-05-22 --kind batch-push \
-//     --versions 0.6.21,0.6.22 --summary "..."
-//
-// Optional flags:
-//   --tag-commit <sha>       (default: HEAD)
-//   --release-commit <sha>   (default: tag-commit)
-//   --scope <key=value,...>  shorthand for the .scope.{key} block
-//   --note "<text>"          append to .notes array; repeatable
-//   --interactive            prompt for missing required fields
-//   --dry                    print to stdout without writing
-//
-// Phase 3 of the adia-ui-release skill. Mechanizes the per-cycle ledger
-// authoring used at Step 11 of cycle-happy-path.
-
-import fs from 'node:fs';
-import path from 'node:path';
-import { execSync } from 'node:child_process';
-import process from 'node:process';
-import { assertMonorepoRoot } from './assert-monorepo-root.mjs';
-
-function parseArgs(argv) {
-  const args = {
-    version: null,
-    date: null,
-    kind: 'release-cut',
-    summary: null,
-    versions: null,
-    tagCommit: null,
-    releaseCommit: null,
-    scope: {},
-    notes: [],
-    dry: false,
-    repo: process.cwd(),
-    repoSlug: '<org>/<repo>',
-  };
-  for (let i = 0; i < argv.length; i++) {
-    const k = argv[i];
-    if (k === '--version') args.version = argv[++i];
-    else if (k === '--date') args.date = argv[++i];
-    else if (k === '--kind') args.kind = argv[++i];
-    else if (k === '--summary') args.summary = argv[++i];
-    else if (k === '--versions') args.versions = argv[++i].split(',');
-    else if (k === '--tag-commit') args.tagCommit = argv[++i];
-    else if (k === '--release-commit') args.releaseCommit = argv[++i];
-    else if (k === '--scope') {
-      const pairs = argv[++i].split(',');
-      for (const p of pairs) {
-        const [key, ...val] = p.split('=');
-        args.scope[key] = val.join('=');
-      }
-    } else if (k === '--note') args.notes.push(argv[++i]);
-    else if (k === '--dry') args.dry = true;
-    else if (k === '--repo') args.repo = argv[++i];
-    else if (k === '--repo-slug') args.repoSlug = argv[++i];
-    else if (k === '-h' || k === '--help') {
-      console.log('Usage: node make-ledger.mjs --version X.Y.Z --date YYYY-MM-DD --summary "..." [--kind release-cut|batch-push|p1-hotfix] [--repo-slug <org>/<repo>] [--tag-commit <sha>] [--release-commit <sha>] [--scope key=val,...] [--note "..."] [--dry]');
-      process.exit(0);
-    }
-  }
-  if (!args.version || !args.date || !args.summary) {
-    console.error('error: --version, --date, --summary all required');
-    process.exit(2);
-  }
-  // Fail-fast guard: refuse to run git against a non-monorepo directory.
-  assertMonorepoRoot(args.repo);
-  if (!args.tagCommit) {
-    args.tagCommit = execSync(`git -C "${args.repo}" rev-parse HEAD`).toString().trim();
-  }
-  if (!args.releaseCommit) args.releaseCommit = args.tagCommit;
-  // Auto-fill repoSlug from the git remote when not explicitly passed — avoids the
-  // '<org>/<repo>' placeholder shipping in the ledger (CodeRabbit-flagged on the
-  // v0.7.17 cut). Falls back to the placeholder if there's no origin remote.
-  if (args.repoSlug === '<org>/<repo>') {
-    try {
-      const url = execSync(`git -C "${args.repo}" remote get-url origin`).toString().trim();
-      const m = url.match(/[:/]([^/]+\/[^/]+?)(?:\.git)?\/?$/);
-      if (m) args.repoSlug = m[1];
-    } catch { /* no remote — leave the placeholder */ }
-  }
-  return args;
-}
-
-function collectTags(repo, version) {
-  const out = execSync(`git -C "${repo}" tag --list 'v${version}' '*-v${version}'`).toString().trim();
-  return out.split('\n').filter(Boolean).sort();
-}
-
-function buildLedger(args) {
-  const isBatch = args.kind === 'batch-push';
-  const allTags = isBatch && args.versions
-    ? args.versions.flatMap((v) => collectTags(args.repo, v))
-    : collectTags(args.repo, args.version);
-
-  const ledger = {
-    kind: args.kind,
-    audit_id: `${args.date}-${args.kind}-v${args.version}`,
-    repo: args.repoSlug,
-    released_at: args.date,
-    version: args.version,
-    release_type: 'PATCH',
-    summary: args.summary,
-  };
-
-  if (Object.keys(args.scope).length > 0) ledger.scope = args.scope;
-  if (isBatch && args.versions) {
-    ledger.versions = args.versions;
-    ledger.tag_commits = {};
-    for (const v of args.versions) {
-      const tag = `v${v}`;
-      try {
-        ledger.tag_commits[tag] = execSync(`git -C "${args.repo}" rev-parse ${tag}`).toString().trim();
-      } catch {
-        ledger.tag_commits[tag] = '<missing — tag not found>';
-      }
-    }
-  } else {
-    ledger.release_commit = args.releaseCommit;
-    ledger.tag_commit = args.tagCommit;
-  }
-
-  ledger.tags = allTags;
-  ledger.verification = {
-    note: 'TODO: paste gate-by-gate summary here. See ledger-discipline.md § canonical schema.',
-  };
-  ledger.publish_workflows = {
-    dispatched: 'TODO: dispatch method (per-package tag-push, one-at-a-time / gh workflow run)',
-    conclusions: '9/9 success',
-  };
-  ledger.notes = args.notes.length > 0 ? args.notes : ['TODO: at least one note per cycle.'];
-
-  return ledger;
-}
-
-function writeOrPrint(ledger, args) {
-  const filename = `${ledger.audit_id}.json`;
-  const target = path.join(args.repo, '.brain', 'audit-history', filename);
-  const content = JSON.stringify(ledger, null, 2) + '\n';
-
-  if (args.dry) {
-    console.log(`[dry] would write to: ${target}`);
-    console.log('---');
-    console.log(content);
-    return;
-  }
-
-  fs.mkdirSync(path.dirname(target), { recursive: true });
-  if (fs.existsSync(target)) {
-    console.error(`error: ${target} already exists. Use --dry to preview or remove it manually.`);
-    process.exit(1);
-  }
-  fs.writeFileSync(target, content);
-  console.log(`[make-ledger] wrote ${target}`);
-  // Nudge: the gate summary + notes can't be auto-derived — warn if TODO stubs
-  // would ship (the v0.7.17 ledger shipped with these; CodeRabbit-flagged).
-  const stubs = [];
-  if (/TODO/.test(ledger.verification?.note || '')) stubs.push('verification');
-  if (/TODO/.test(ledger.publish_workflows?.dispatched || '')) stubs.push('publish_workflows.dispatched');
-  if ((ledger.notes || []).some((n) => /TODO/.test(n))) stubs.push('notes');
-  if (ledger.repo === '<org>/<repo>') stubs.push('repo');
-  if (stubs.length) {
-    console.warn(`\n⚠ [make-ledger] ${stubs.length} field(s) still placeholder — FILL before committing: ${stubs.join(', ')}`);
-    console.warn(`  (repo auto-fills from the git remote; pass --note "..." + hand-edit verification / publish_workflows)`);
-  }
-  console.log(`\n[next] verify the ledger:`);
-  console.log(`  cat ${target} | jq .`);
-  console.log(`\n[next] commit + push:`);
-  console.log(`  git add ${target}`);
-  console.log(`  git commit -m "chore(audit-history): v${ledger.version} release ledger"`);
-  console.log(`  git push origin main`);
-}
-
-function main() {
-  const args = parseArgs(process.argv.slice(2));
-  const ledger = buildLedger(args);
-  writeOrPrint(ledger, args);
-}
-
-try {
-  main();
-} catch (e) {
-  console.error(`error: ${e.message}`);
-  process.exit(1);
-}

package/skills/adia-ui-release/skill.json

@@ -1,77 +0,0 @@
-{
-  "name": "adia-ui-release",
-  "version": "0.2.2",
-  "description": "Release engineer for an @adia-ai-style lockstep monorepo. Cuts, tags, publishes, deploys, authors release notes + audit-history ledgers \u2014 AND authors the MIGRATION GUIDE when a cut breaks an API (the producer side of migrations, folded in from the former adia-ui-migration skill). Also ships an INDEPENDENT-PACKAGE (class-B) release path for packages versioned independently of the lockstep set (excluded from the lockstep gate, no umbrella tag, no demo-site deploy \u2014 e.g. plugins). Use whenever the user wants to CUT A RELEASE / SHIP A VERSION / PUBLISH PACKAGES / BATCH-PUSH ACCUMULATED RELEASES / RECOVER FROM A VERSION-SKIP / WRITE RELEASE NOTES / PROMOTE [UNRELEASED] CHANGELOG / AUTHOR A MIGRATION GUIDE FOR A BREAKING CUT / SHIP AN INDEPENDENTLY-VERSIONED PACKAGE OR PLUGIN. Triggers on \"cut vX.Y.Z\", \"initiate a release\", \"publish the npm packages\", \"tag this commit and push the release\", \"batch push\", \"F-N1 warned\", \"GitHub release notes\", \"promote unreleased\", \"version skip recovery\", \"verify pre-flight gates\", \"the cycle just shipped \u2014 write up what happened\", \"author a migration guide / write the migration recipe for this breaking change\", \"release the plugin / ship an independently-versioned package / publish a package outside the lockstep\". VERIFICATION is load-bearing: every cut verifies against reality (npm registry + production endpoint + GH release), not self-checks. Carries the portable release DISCIPLINE with the @adia-ai monorepo's 9-package lockstep + demo-site deploy as the clearly-labeled worked example. Does NOT trigger for: the CONSUMER side of migration (sweeping a downstream app \u2014 the separate consumer/app-author plugin), long-running VM ops (provision/restart/key rotation), authoring new code, or generation-pipeline work.",
-  "status": "stable",
-  "authors": [
-    "kim.granlund"
-  ],
-  "tags": [
-    "adia-ui",
-    "release",
-    "publish",
-    "lockstep",
-    "release-notes",
-    "migration-guide",
-    "producer-side"
-  ],
-  "environment": {
-    "portable": false,
-    "requires": [
-      "an @adia-ai-style lockstep monorepo: @adia-ai/* packages under packages/* that version + publish together, with per-package CHANGELOG.md, a release trip-wire, and a publish-workflow per package"
-    ],
-    "rationale": "The skill mutates a real monorepo (commits, tags, lockfiles) and triggers real package publishes; the gate roster, deploy target, and ledger paths are substrate-bound. The DISCIPLINE generalizes to any @adia-ai-style lockstep monorepo, but the worked example (9-package lockstep, ui-kit.exe.xyz deploy) is the @adia-ai monorepo specifically."
-  },
-  "files": [
-    "SKILL.md",
-    "skill.json",
-    "CHANGELOG.md",
-    "references/cycle-happy-path.md",
-    "references/multi-agent-baseline.md",
-    "references/gates-catalog.md",
-    "references/recovery-paths.md",
-    "references/changelog-discipline.md",
-    "references/notes-authoring.md",
-    "references/rollup-notes.md",
-    "references/exe-deploy.md",
-    "references/ledger-discipline.md",
-    "references/migration-guide-authoring.md",
-    "references/independent-package-release.md",
-    "references/teach-protocol.md",
-    "scripts/bump.mjs",
-    "scripts/promote-unreleased.mjs",
-    "scripts/insert-stub.mjs",
-    "scripts/package-paths.mjs",
-    "scripts/tag-lockstep.mjs",
-    "scripts/dispatch-publish.mjs",
-    "scripts/make-ledger.mjs",
-    "scripts/release-pack.mjs",
-    "scripts/audit-gate-roster.mjs",
-    "assets/templates/stub-changelog.template.md",
-    "assets/case-studies/2026-05-20-version-skip-correction-v0.6.12.md",
-    "assets/case-studies/2026-05-20-batch-push-v0.6.14-v0.6.15.md",
-    "assets/case-studies/2026-05-20-corpus-drift-remediation-v0.6.15.md",
-    "assets/case-studies/2026-05-21-author-from-scratch-v0.6.18.md",
-    "assets/case-studies/2026-05-21-fn1-enrichment-pass-v0.6.19.md",
-    "assets/case-studies/2026-05-21-stale-test-detection-v0.6.20.md",
-    "assets/case-studies/2026-05-21-feedback37-retraction-v0.6.21.md",
-    "assets/case-studies/2026-05-23-freshness-gate-recovery-v0.6.32.md",
-    "assets/case-studies/2026-05-26-catalog-drift-recurring-v0.6.40.md",
-    "evals/evals.json"
-  ],
-  "peer_skills": [
-    "adia-ui-authoring",
-    "adia-ui-a2ui",
-    "adia-ui-dogfood",
-    "ops-postmortem"
-  ],
-  "absorbs": [
-    "adia-ui-migration \u2014 DONE: producer side folded in as references/migration-guide-authoring.md + mode 11 (\u00a7MigrationGuideAuthoring). The consumer side stays in the separate consumer/app-author plugin.",
-    "release-publish / release-notes / verification-sweep \u2014 DONE in the source skill: consolidated into modes 1/3/4 (cut), 5/9 (notes), 6 (verify)."
-  ],
-  "references": [
-    "adia-ui-a2ui \u2014 corpus-freshness checks route there for remediation (verify:corpus / embeddings drift)",
-    "adia-ui-dogfood \u2014 the static-HTML probes (native-primitive-leak, shell-composition) whose findings fold into release notes",
-    "ops-postmortem \u2014 incident genre during post-publish recovery (mode 7)"
-  ]
-}

package/skills/dogfood-sweep/CHANGELOG.md

@@ -1,37 +0,0 @@
-# Changelog — dogfood-sweep
-
-## [0.1.0] stable — 2026-05-24
-
-**MINOR** — first versioned cut. Adds `skill.json` + `CHANGELOG.md` to bring
-the skill into rollup-family conventions (per META-REFACTOR-SPEC Round 0).
-No procedural changes to the 6 modes.
-
-The skill is otherwise unchanged: SKILL.md still carries all 6 modes inline
-(component visual probe / app-shell QA / HTML typo sweep / native-primitive
-leak / admin-shell composition / component anatomy + card header). The
-inversion to `references/mode-N-*.md` is Round 2+ work per the per-skill
-REFACTOR-SPEC at `docs/REFACTOR-SPEC.md`.
-
-### Reconstructed history (pre-v0.1.0)
-
-- **2026-05-04** — Added probe #6 (missing component CSS detection) to mode 1
-  after the swap-to-primitive-but-forget-the-link class slipped past a real
-  PR. The bug class: agent uses `<button-ui>` markup but forgets the
-  `<link rel="stylesheet">` for the button component CSS; element registers,
-  markup looks right, listbox renders unstyled.
-
-- **post-§3 commit** — Native-primitive-leak audit (mode 4) intent-marker
-  detection window widened from 80 → 200 chars after a peer agent found that
-  realistic preceding-line comments (indent + comment prefix + reason text +
-  closing `-->` + newline) sat at exactly the 80-char boundary and were not
-  detected.
-
-- **v2.27.4-era** — Mode 6 (Component Anatomy + Card Header Sweep) added per
-  FB-52 §11: card-ui `<header><div>` wrapper anti-pattern + missing anatomy
-  sections per `anatomy-sweep.mjs` expectations.
-
-- **Pre-versioned origin** — Mode 1 (component visual probe via Chromium)
-  authored as the initial skill. Modes 2–5 absorbed from substrate-side
-  `scripts/dev/audit-*.mjs` work over multiple cycles. The skill grew its
-  6-mode catalog organically; this v0.1.0 cut is the first time the manifest
-  reflects the actual content.

package/skills/dogfood-sweep/README.md

@@ -1,105 +0,0 @@
-# Dogfooding analyzer
-
-Walks every `/site/components/*` demo page in headless Chromium and runs
-visual-correctness probes that type-checks and tests don't catch:
-
-| # | Probe | Bug class it detects |
-|---|-------|----------------------|
-| 1 | Zero-area | Element collapsed (parent `display:none`, toolbar overflow spilled it, layout glitch) |
-| 2 | Transparent fill | `[data-swatch]` / variant pill / button / chart indicator whose computed bg is `rgba(0,0,0,0)` — fallback token doesn't resolve (the chart-legend `--chart-N` class) |
-| 3 | Empty control | `input-ui` / `search-ui` / `button-ui` / `select-ui` / `tag-ui` whose `connected()` should have stamped internals but didn't |
-| 4 | Synonym-attr / synonym-slot drift | Markers from `docs/conventions/attribute-api-migration.md` (`avatar-ui[name]`, `grid-ui[cols]`, `card-ui [slot=meta]`, etc.) |
-| 5 | Alert flex-row | `alert-ui` with multiple bare `<text-ui>` children (need `<col-ui slot="content">` wrap) |
-| 6 | Console | Every `console.error` + `console.warn` during page load + 800ms settling |
-
-Output: severity-ranked markdown report at
-`docs/reports/dogfooding-YYYY-MM-DD.md`.
-
-## Run locally
-
-```bash
-# Terminal 1
-npm run dev
-
-# Terminal 2
-node .agents/skills/dogfood-sweep/analyze.mjs                    # full sweep (~82 pages)
-node .agents/skills/dogfood-sweep/analyze.mjs --filter chart-legend  # one page
-node .agents/skills/dogfood-sweep/analyze.mjs --port 5174            # custom port
-node .agents/skills/dogfood-sweep/analyze.mjs --out /tmp/r.md        # custom path
-```
-
-Exit code: **1** if any **critical** findings, **0** otherwise. CI-friendly.
-
-## Schedule as a remote agent
-
-The script is the data gatherer. The remote agent wraps it with git
-orchestration: clone repo, start dev server, run script, triage findings,
-commit/PR.
-
-Agent prompt (use `/schedule` skill to register; weekly cadence
-recommended — pages drift slowly):
-
-```
-You are the AdiaUI dogfooding agent. Your job is to find visual bugs in
-the component demo pages that type-checks miss.
-
-1. `npm install --frozen-lockfile`
-2. Start the dev server in the background:
-     npm run dev > /tmp/vite.log 2>&1 &
-   Wait for "ready" in /tmp/vite.log (max 30s).
-3. `node .agents/skills/dogfood-sweep/analyze.mjs`
-   The script writes `docs/reports/dogfooding-YYYY-MM-DD.md` and exits
-   non-zero iff any critical findings.
-4. Read the report. For each *critical* finding, evaluate independently:
-   - Is the diagnosis right? (cross-check with component source)
-   - Is the fix mechanical and unambiguous?
-   - Does memory or `attribute-api-migration.md` already document the
-     pattern?
-5. If yes to all three → apply the fix, run the verification gate
-   (`node scripts/build/components.mjs --verify && npm run test:a2ui`),
-   and include the diff in the PR.
-6. If the diagnosis is right but the fix is non-trivial → leave it for
-   a human, just file the report.
-7. Open a PR titled "dogfood: <date> — <N> critical, <M> warning":
-   - body = first 100 lines of the report
-   - link to the full report file
-   - if you applied any fixes, list them as a checklist
-8. If 0 critical and 0 warning, still commit the report file (under
-   `docs/reports/`) so we have a paper trail of "things were fine".
-9. Stop the dev server before exiting.
-
-Hard rules:
-- Never touch `packages/web-components/components/avatar/avatar.js:48`
-  (the deprecation handler string) when sweeping `<avatar-ui name=…>`.
-- Never edit `MIGRATION GUIDE.md` historic sections; only the active
-  v0.0.X section.
-- Don't fix more than 5 critical findings in one PR — leave the rest
-  for follow-up so humans can review fix shape before scaling.
-```
-
-Register via `/schedule weekly node .agents/skills/dogfood-sweep/analyze.mjs` or
-hand-author with the agent prompt above.
-
-## False positives + tuning
-
-The probes are intentionally narrow. Known places where "transparent
-fill" is by design (and shouldn't be added to `COLORED_SELECTORS`):
-
-- `tag-ui` without a variant (`muted` / default) — bg is correctly
-  `--a-bg-muted`, not transparent.
-- `button-ui[variant=ghost]` — transparent by design.
-- `[data-swatch]` for `chart-legend-ui[shape=dashed]` — intentionally
-  transparent bg + colored `border-top`. The probe handles this case.
-
-If a finding is a known false positive, add the parent component or
-selector to the skip-list rather than removing it from
-`COLORED_SELECTORS` (preserves coverage on the canonical case).
-
-## When to revisit the probe set
-
-- New component ships → add to `STAMP_CONTRACTS` if it has internal
-  stamping logic.
-- New synonym-attribute drift class documented in
-  `attribute-api-migration.md` → add to `DRIFT_MARKERS`.
-- A class of bugs slips past the analyzer in a real PR → add a probe
-  for that bug class first, *then* fix it. Test for the test.