Skip to content

chore(registry): update audit + CONTRIBUTING to cover drift script - #4

Merged
codewizdave merged 1 commit into
mainfrom
chore/post-merge-audit-followups
Jul 29, 2026
Merged

chore(registry): update audit + CONTRIBUTING to cover drift script#4
codewizdave merged 1 commit into
mainfrom
chore/post-merge-audit-followups

Conversation

@martyy-code

Copy link
Copy Markdown
Contributor

Summary

Two small doc updates post PR #3, both addressing gaps the
drift script reveals about contributor onboarding.

What's in this PR

1. CONTRIBUTING.md — steps 7 & 8 in the addition flow

Adding a new ds-* component without updating the audit
JSON would land with a red drift CI job that the
contributor can't debug (it fails closed for un-audited
items). Step 7 makes the audit update part of the
addition flow:

{
  "items": {
    "ds-<id>": {
      "showcase-category": "shim",
      "consumer-path": "registry/base-nova/ds-<id>/ds-<id>.tsx",
      "showcase-path": "packages/registry/src/components/<id>/index.tsx",
      "workspace-source-path": "packages/ui/src/components/<id>.tsx"
    }
  }
}

Step 8 ("run the drift script locally") catches drift
between the new consumer source and the showcase tree
before pushing — saves a CI round-trip and a clean-up
commit.

2. docs/registry/audit-2026-07-29.json — version bump + state update

Bumped from 2026-07-29 to 2026-07-29-b. The
ds-colored-badge entry is updated to reflect the
post-fix state (PR #3 commits d90b7d9 and e2e47a4):

  • concrete-divergence-observed: false
  • The two commits are listed in a new
    concrete-divergence-resolved-by field
  • divergence-detail documents what the showcase and
    consumer now render (still Badge primitive vs raw span,
    but the span inlines the Badge's class strings so they
    produce visually equivalent output)
  • per-check and recommended-fix reflect the new
    state (no fix needed; drift script will catch future
    silent drift)

CI: unchanged. Doc-only edits do not affect the registry
catalog, the build pipeline, the drift script, or any of
the 6 CI jobs. All 5 of the existing jobs should report
green on this PR (the 6th, drift, runs in 10s and exits 0).

🤖 Generated with Claude Code

…post-PR-3 state

Two small follow-ups post PR #3:

1. CONTRIBUTING: steps 7 and 8 added — extending the
   'Adding a new ds-* component' flow with (a) updating
   docs/registry/audit-YYYY-MM-DD.json so the drift CI job
   has per-item paths and classifications, and (b) running
   the drift script locally before pushing. Without step 7,
   adding a new item would land with a red drift job that
   nobody had warned the contributor about.

2. Audit JSON: version bumped to 2026-07-29-b, ds-colored-badge
   fields updated to reflect the post-fix state:
   - concrete-divergence-observed: false (d90b7d9 + e2e47a4
     resolved both the structural divergence and the
     bg-blue-500 -> bg-blue-600 shade bump across both trees)
   - divergence-detail expanded to explain the showcase and
     consumer render targets and the equivalent visual classes
   - per-check updated from FAIL to structural-pass-via-inline
   - concrete-divergence-resolved-by field lists the two
     commits that resolved it

No code change. CI excludes drift, lint, typecheck,
contract, registry-validate, build-showcase all unaffected
by doc-only edits.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ui-web Ready Ready Preview, Comment Jul 29, 2026 11:43am

@codewizdave
codewizdave merged commit 3a05e4c into main Jul 29, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants