chore: add component-status manifest sync check to lint pipeline

[QuintonJason]

Description

Adds a CI-gated check that keeps libs/core/src/stories/resources/component-status.json (the declared source of truth for StatusBadge and the central Component status table) in sync with libs/core/src/components/, so the two cannot silently drift after the lifecycle-status work landed in #738 / #748.

The check fails the build when:

• a top-level pds-* component has no status entry, or
• a status entry references a pds-* that no longer exists.

Manifest entries validate against any pds-* directory (top-level or a nested subcomponent such as pds-filter), so deliberate subcomponent entries pass without a hardcoded allowlist.

Why no workflow changes: CI runs nx affected --target=lint → core's lint script → run-p lint.*. Adding lint.status means the existing lint job gates this automatically — no new workflow YAML or composite action.

New dependencies: none (dependency-free ESM Node script).

Fixes #(no-issue)

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Passes on current main (36 entries in sync).

• Verified it fails with an actionable message when an entry is removed (pds-button) and when a stale entry is added (pds-ghost), then confirmed clean after restore.

• npm run lint.status resolves; run-p lint.* enumerates lint.eslint, lint.status, lint.styles.

• unit tests

• e2e tests

• accessibility tests

• tested manually

• other: self-validating check run against real + simulated drift

Test Configuration:

• Pine versions: 3.26.1 (current main)
• OS: macOS 25.3.0
• Browsers: n/a
• Screen readers: n/a
• Misc: tooling-only change

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• Design has QA'ed and approved this PR

---

Note

Low Risk
Tooling-only changes with no runtime component or API behavior; risk is limited to CI failing until manifests, waivers, or mappings are updated.

Overview
Adds two maturity checks to @pine-ds/core lint (run-p lint.*), so existing nx affected --target=lint CI picks them up without workflow changes.

lint.status keeps component-status.json aligned with src/components/: every top-level pds-* must have a manifest entry, and every entry must match a real pds-* directory (including nested subcomponents). lint.figma requires each top-level component to have a libs/figma/components/<name>.figma.ts mapping or an explicit waiver in code-connect-waivers.json, and reports redundant/orphan waivers.

Shared enumeration lives in scripts/lib/components.mjs. Nx now treats @pine-ds/figma as an implicit dependency of core and extends lint inputs to figma waivers and *.figma.ts so cache and affected lint stay correct when only figma changes. A minimal libs/figma workspace package is registered in the lockfile.

^{Reviewed by Cursor Bugbot for commit 0632cd7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[netlify]

✅ Deploy Preview for pine-design-system ready!

Name	Link
🔨 Latest commit	0632cd7
🔍 Latest deploy log	https://app.netlify.com/projects/pine-design-system/deploys/6a230ca9ecc1540008714b7a
😎 Deploy Preview	https://deploy-preview-750--pine-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pixelflips]

Should be fine for now, but I still think it's worth letting Storybook handle these, but nothing is blocking from a code review standpoint.