@lifeaitools/rdc-skills 0.9.38 → 0.11.0

package/guides/history-md-spec.md

@@ -0,0 +1,297 @@
+---
+type: spec
+role: history-md
+systems: [place-fund, prt, plan]
+schema_version: "1.0"
+tags: [history-md, spec, rdc-skills, place-fund]
+---
+# HISTORY.md — Authoritative Specification
+> Version: 1.0 | Effective: 2026-05-22
+
+Every land-based project in the Place Fund ecosystem that satisfies the trigger predicate below
+MUST carry a `places/<prt_slug>/HISTORY.md` file in the regen-root monorepo.
+Skills that plan, scaffold, and validate real-estate PRT projects read this file to verify
+research provenance, lineage completeness, and research lifecycle status.
+
+---
+
+## Purpose
+
+`HISTORY.md` is the **land lineage record** for a Place Fund project — the authoritative
+document linking a `prt_projects` row to its physical, ecological, cultural, and regulatory
+history. It is NOT a marketing document. It is a research-grade provenance record that:
+
+- Provides due-diligence depth for regenerative land stewardship decisions
+- Anchors the project's data to verifiable primary sources (county records, PLSS, BLM, state archives)
+- Tracks research lifecycle from `draft` through `peer-reviewed` so consumers know what to trust
+- Enables the Place Fund's ecological and conservation underwriting to be audited independently
+
+A missing or stub `HISTORY.md` signals that research is pending. A `published` one signals
+that the record has been reviewed and is fit for external use.
+
+---
+
+## Trigger Predicate
+
+A `prt_projects` row **requires** a `places/<slug>/HISTORY.md` when ALL of:
+
+1. `project_type IN ('ranch','eco-hospitality','mixed','conservation','regenerative-agriculture','real-estate','development')`
+2. `name IS NOT NULL` (always true for active rows)
+3. AT LEAST ONE OF:
+   - `location_state IS NOT NULL`
+   - `location_city IS NOT NULL`
+   - `country IS NOT NULL`
+   - `total_acres IS NOT NULL`
+   - `lat IS NOT NULL`
+   - `EXISTS (SELECT 1 FROM geo_parcels WHERE project_id = prt_projects.id)`
+   - `EXISTS (SELECT 1 FROM geo_projects WHERE prt_project_id = prt_projects.id)` — a geo_projects join indicates real GIS data exists for this place, even if lat/lng on prt_projects is unset
+
+**Excluded by default:** `project_type IN ('credit','water','tech','regenerative-model')` — these
+are credit instruments or abstract models, not physical land parcels. Individual rows may be
+opted in manually by a supervisor if a composite history is warranted.
+
+As a SQL check (used by the validator):
+
+```sql
+SELECT slug, name, project_type, location_state, location_city, country, total_acres, lat
+FROM prt_projects
+WHERE is_template IS NOT TRUE
+  AND project_type IN ('ranch','eco-hospitality','mixed','conservation',
+                       'regenerative-agriculture','real-estate','development')
+  AND (
+    location_state IS NOT NULL
+    OR location_city IS NOT NULL
+    OR country IS NOT NULL
+    OR total_acres IS NOT NULL
+    OR lat IS NOT NULL
+    OR EXISTS (SELECT 1 FROM geo_parcels WHERE project_id = prt_projects.id)
+    OR EXISTS (SELECT 1 FROM geo_projects WHERE prt_project_id = prt_projects.id)
+  )
+ORDER BY slug;
+```
+
+---
+
+## Schema
+
+### Frontmatter Fields
+
+Every `HISTORY.md` begins with YAML frontmatter bounded by `---` delimiters.
+
+```yaml
+---
+schema_version: "1.0"
+prt_slug: SLUG
+project_type: ranch
+location:
+  county: COUNTY
+  state: STATE
+  country: COUNTRY
+  parcel_apn: APN
+  area_acres: ACRES
+  centroid: [LAT, LNG]
+acquired: "YYYY-MM-DD"
+steward: STEWARD_NAME
+research_status: draft
+last_reviewed: "YYYY-MM-DD"
+contributors: []
+---
+```
+
+### Field Reference
+
+| Field | Type | Required | Notes |
+|-------|------|----------|-------|
+| `schema_version` | string | yes | Always `"1.0"` for this revision |
+| `prt_slug` | string | yes | Must match `prt_projects.slug` exactly (case-sensitive) |
+| `project_type` | string | yes | Echo from `prt_projects.project_type` |
+| `location` | object | yes | Nested block — see sub-fields below |
+| `location.county` | string | no | County or district name |
+| `location.state` | string | no | State or province name or abbreviation |
+| `location.country` | string | no | Country name; omit if USA |
+| `location.parcel_apn` | string | no | Assessor's Parcel Number (APN) or equivalent |
+| `location.area_acres` | number | no | Total acreage from authoritative source |
+| `location.centroid` | [lat, lng] | no | Decimal-degree centroid coordinates |
+| `acquired` | ISO date | no | Acquisition date (`YYYY-MM-DD`); omit if unknown |
+| `steward` | string | yes | Current stewarding entity or person |
+| `research_status` | enum | yes | One of: `draft` · `in-research` · `peer-reviewed` · `published` |
+| `last_reviewed` | ISO date | yes | Date this file was last substantively reviewed |
+| `contributors` | string[] | yes | Array of contributor identifiers (may be empty `[]`) |
+
+#### `research_status` semantics
+
+| Value | Meaning |
+|-------|---------|
+| `draft` | Stub created; no primary-source research yet |
+| `in-research` | Active research underway; primary sources being identified |
+| `peer-reviewed` | Research complete; reviewed by at least one secondary reviewer |
+| `published` | Record approved for external publication and citation |
+
+The validator will warn (not fail) on `draft` rows — they are expected during initial rollout.
+The validator will fail if `research_status` is not one of the four allowed values.
+
+---
+
+## Required Body Sections
+
+The body of `HISTORY.md` must contain all five section headings in order. Each section may
+contain a TODO marker during draft status; it must contain substantive prose at `published`.
+
+### `## Land lineage`
+
+Deep time through present ownership. Cover:
+- Pre-contact landscape and ecological baseline
+- Indigenous stewardship, use patterns, and territorial context
+- Spanish/Mexican land grants (if applicable)
+- US government survey and PLSS reference (township, range, section)
+- Homestead entry, patent, and early title chain
+- Major ownership transitions to present
+
+### `## Stewardship transitions`
+
+Timeline of stewardship changes. Cover:
+- Each major ownership or management transfer with approximate dates
+- Conservation easements, deed restrictions, and encumbrances
+- Use-change inflection points (e.g. dryland → irrigated, grazing → timber)
+- Current stewardship entity and tenure
+
+### `## Ecological context`
+
+Physical and biological baseline. Cover:
+- Ecoregion and watershed affiliation
+- Soil classifications (NRCS Web Soil Survey references)
+- Vegetation communities and cover types
+- Water resources (streams, springs, riparian areas, aquifer)
+- Wildlife corridors and listed species presence/absence
+- Fire history and disturbance regime
+
+### `## Cultural significance`
+
+Human geography and intangible values. Cover:
+- Indigenous place names and cultural associations (cite tribal consultation if any)
+- Historic structures, archaeological sites, or cultural landscapes (Section 106 if applicable)
+- Community significance — grazing allotments, water rights, access traditions
+- Scenic and recreational values
+
+### `## Regulatory record`
+
+Legal, regulatory, and administrative context. Cover:
+- Zoning and land use designations
+- Conservation easements held by land trusts (ACE, TNC, CLT, etc.)
+- Water rights adjudications
+- Federal and state permits (grazing permits, NEPA actions, ESA consultations)
+- Tax status (agricultural classification, conservation land designation)
+- Open title or lien issues of record
+
+---
+
+## File Location Convention
+
+```
+C:/Dev/regen-root/places/<prt_slug>/HISTORY.md
+```
+
+The directory is named using the **sanitized slug** — lowercase, no special characters,
+hyphens for separators. If `prt_projects.slug` contains uppercase letters (e.g. `Diamond`),
+the filesystem path uses `diamond/HISTORY.md` while `prt_slug` in frontmatter preserves
+the exact DB value (`Diamond`).
+
+---
+
+## Enforcement Layers
+
+### Layer 1 — Workflow scaffold (`rdc:plan`)
+
+When `rdc:plan` creates a new `prt_projects` row with a qualifying `project_type`, it reads
+this spec and produces a stub `places/<slug>/HISTORY.md` from `scaffold/templates/HISTORY.md.template`.
+The stub is committed alongside the epic creation commit so the file is never absent from day one.
+
+### Layer 2 — Validator script
+
+`C:/Dev/rdc-skills/scripts/validate-place-histories.js` runs in two modes:
+
+| Mode | Behavior | Exit code |
+|------|----------|-----------|
+| `--mode warn` (default) | Missing or malformed HISTORY.md emits WARN; exits 0 | 0 |
+| `--mode fail` | Missing or malformed HISTORY.md emits FAIL; exits 1 | 1 |
+
+The validator is wired into the `rdc-skills` `prepack` step (warn mode) so it runs on every
+package publish and surfaces gaps without blocking.
+
+### Layer 3 — Optional DB gate (future)
+
+A `history_md_status` column on `prt_projects` can mirror `research_status` from frontmatter
+via a sync script. This enables Supabase-side filtering of projects by research completeness.
+Not implemented in v1 — planned for a future epic.
+
+---
+
+## Consumer Integration
+
+### `rdc:plan`
+
+When scaffolding a new real-estate PRT project:
+1. Check if `project_type` satisfies the trigger predicate.
+2. If yes: hydrate `HISTORY.md.template` with DB row metadata and write `places/<slug>/HISTORY.md`.
+3. Commit the stub alongside the epic creation commit.
+
+### `rdc:review` / `rdc:build`
+
+When the build scope touches `apps/prt/`:
+1. Run `node C:/Dev/rdc-skills/scripts/validate-place-histories.js --mode warn`.
+2. Surface any WARN lines in the review output.
+3. Do not block on warn — block only on FAIL (malformed frontmatter).
+
+---
+
+## Example — Dos Pueblos Ranch (dp-phased-model)
+
+```markdown
+---
+schema_version: "1.0"
+prt_slug: dp-phased-model
+project_type: ranch
+location:
+  county: Santa Barbara
+  state: California
+  country:
+  parcel_apn:
+  area_acres:
+  centroid:
+acquired:
+steward: Dos Pueblos Ranch LLC
+research_status: draft
+last_reviewed: "2026-05-22"
+contributors: []
+---
+
+> This is a draft stub. Research pending. Status will be promoted to in-research once primary sources are identified.
+
+## Land lineage
+
+TODO: Research land lineage of Dos Pueblos Ranch. Cover Chumash territory, Spanish rancho land grant (Rancho Dos Pueblos, c. 1842), Mexican land commission adjudication, US patent, and ownership chain to present.
+
+## Stewardship transitions
+
+TODO: Document major ownership and use transitions for Dos Pueblos Ranch from rancho era through current orchid and agricultural operations.
+
+## Ecological context
+
+TODO: Document ecoregion (Southern California Coast Ranges), chaparral and oak woodland communities, seasonal streams, and proximity to coastal wetlands.
+
+## Cultural significance
+
+TODO: Research Chumash place names and village associations. Note proximity to historic Chumash settlements along the Santa Barbara coast.
+
+## Regulatory record
+
+TODO: Document zoning (Santa Barbara County agricultural/rural zones), any conservation easements, and water rights in Goleta Water District service area.
+```
+
+---
+
+## Changelog
+
+| Version | Date | Change |
+|---------|------|--------|
+| 1.0 | 2026-05-22 | Initial spec — trigger predicate, schema, 5 required sections, 3-layer enforcement |

package/guides/publish-md-spec.md

@@ -0,0 +1,289 @@
+---
+type: spec
+role: publish-md
+systems: [deploy, release, plan]
+schema_version: "1.0"
+tags: [publish-md, spec, rdc-skills]
+---
+# PUBLISH.md — Authoritative Specification
+> Version: 1.0 | Effective: 2026-05-22
+> Architectural approval: 2026-05-22 interview (Option A — Full Rollout)
+
+Every deployable target in the RDC ecosystem MAY carry a `PUBLISH.md` file
+in its root directory. Skills that deploy, release, and plan read this file
+to derive watch paths, surface metadata, and promotion gates.
+
+---
+
+## Schema
+
+A `PUBLISH.md` file consists of two parts:
+
+1. **YAML frontmatter** — app-level metadata, bounded by `---` delimiters.
+2. **One or more surface sections** — per-surface metadata, bounded by
+   HTML comment markers (`<!-- SURFACE:<name> -->` … `<!-- /SURFACE:<name> -->`).
+
+Frontmatter is authoritative. Surface sections are the publish manifest.
+
+---
+
+## Frontmatter Fields
+
+All fields are required unless marked optional.
+
+```yaml
+---
+schema_version: "1.0"          # (required) always "1.0" for this revision
+entity_slug: <slug>            # (required) matches app_deployments.app_slug
+artifact_type: <type>          # (required) one of: website | api | package | worker | mcp-server
+environments: [dev]            # (required) array; subset of: dev, prod
+status: active                 # (required) one of: active | draft | deprecated
+notes: ""                      # (optional) free-text, ignored by validator
+---
+```
+
+### Field Reference
+
+| Field | Type | Required | Allowed Values |
+|-------|------|----------|---------------|
+| `schema_version` | string | yes | `"1.0"` |
+| `entity_slug` | string | yes | must match `app_deployments.app_slug` |
+| `artifact_type` | string | yes | `website` · `api` · `package` · `worker` · `mcp-server` |
+| `environments` | string[] | yes | subset of `[dev, prod]`; at least one required |
+| `status` | string | yes | `active` · `draft` · `deprecated` |
+| `notes` | string | no | free-text annotation |
+
+#### `environments` semantics
+
+- `[dev]` — surface is only available on the PM2 dev server
+- `[prod]` — surface is only available on the Coolify production instance
+- `[dev, prod]` — surface exists in both tiers
+
+The validator enforces: each value in `environments` must match an
+`app_deployments.environment` row for the same `entity_slug`.
+
+#### `status` semantics
+
+- `active` — `rdc:release` promotion is allowed
+- `draft` — `rdc:release` will block and print a warning; dev deploy is allowed
+- `deprecated` — `rdc:release` will block; validator flags as warn
+
+---
+
+## Surface Sections
+
+Each deployable surface gets one managed section inside the PUBLISH.md body.
+Sections are bounded by HTML comment markers so skills can read and rewrite
+them without clobbering hand-authored prose.
+
+```
+<!-- SURFACE:<name> -->
+path: /
+source_dir: apps/baru-website
+build_type: nextjs
+visibility: public
+cache: no-store
+watch_paths:
+  - apps/baru-website/**
+  - packages/ui/**
+  - packages/supabase/**
+<!-- /SURFACE:<name> -->
+```
+
+### Surface Field Reference
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `path` | string | yes | URL path prefix served by this surface (e.g. `/`, `/api`) |
+| `source_dir` | string | yes | Monorepo-relative path to the source directory |
+| `build_type` | string | yes | `nextjs` · `static` · `docker` · `node` · `edge` |
+| `visibility` | string | yes | `public` · `private` · `internal` |
+| `cache` | string | yes | HTTP cache directive: `no-store` · `immutable` · `stale-while-revalidate` · `max-age=N` |
+| `watch_paths` | string[] | yes | gitignore-style globs; at least one required. These are unioned to derive Coolify `watch_paths`. |
+| `artifact_id` | string | no | Stable ID for `artifact_registry` upserts; defaults to `<entity_slug>/<name>` |
+
+### `<name>` convention
+
+The surface name appears in the comment markers and must be a short,
+lowercase, hyphen-separated identifier that describes the surface:
+
+- `website` — primary web UI
+- `api` — REST/GraphQL API
+- `mcp` — Model Context Protocol server endpoint
+- `worker` — background worker or cron
+- `static` — purely static asset serving
+
+Multiple surfaces are allowed per file (e.g. a Next.js app that also exposes
+an API surface under `/api`).
+
+---
+
+## Environments Array
+
+The top-level `environments` field declares which deployment tiers host this app.
+Each surface inherits the app-level `environments` unless overridden at the
+surface level (not supported in schema v1.0 — planned for v1.1).
+
+Validator enforcement:
+1. At least one environment must be declared.
+2. Each declared environment must be one of `dev` or `prod`.
+3. Each declared environment must have a corresponding `app_deployments` row for the `entity_slug`.
+
+`rdc:deploy` uses `environments` to determine whether a dev or prod deploy is
+appropriate for the given target. `rdc:release` requires `prod` to be present
+before promoting.
+
+---
+
+## Opt-out (File Absence)
+
+**PUBLISH.md absence = opt-out.** There is no sentinel field, no `publish: false`.
+
+A deployable target without a `PUBLISH.md`:
+- Is skipped by `rdc:deploy`'s watch-paths derivation step.
+- Is NOT inserted into `artifact_registry` on deploy.
+- Is flagged as a **warn** (not fail) by the validator during the Option A rollout period.
+- Will become a **fail** once the rollout is complete (controlled by the `--strict` flag on the validator).
+
+Packages and libraries that are not independently deployed (e.g. `@regen/ui`)
+do not require a `PUBLISH.md`. Only targets with a row in `app_deployments` are in scope.
+
+---
+
+## Validator Contract
+
+The validator (`scripts/validate-publish-manifests.js`) operates in two modes:
+
+### Warn mode (default, during rollout)
+
+In warn mode the validator:
+- Queries `app_deployments` for all `status = 'active'` rows.
+- For each row, checks whether a `PUBLISH.md` exists at the expected path.
+- For rows without `PUBLISH.md`: emits a `WARN` line and continues.
+- For rows WITH `PUBLISH.md`: parses YAML frontmatter and validates all required fields.
+- If frontmatter is invalid (missing required field, bad enum value): emits a `FAIL` line.
+- Exits 0 if there are no `FAIL` lines (warns are non-fatal in this mode).
+
+### Strict mode (`--strict`)
+
+In strict mode:
+- Missing `PUBLISH.md` is treated as `FAIL`, not `WARN`.
+- Exits non-zero if any registered active app is missing a manifest.
+- Used in CI after Option A rollout is complete.
+
+### Field validation rules
+
+| Check | Fail condition |
+|-------|---------------|
+| `schema_version` present | missing or not `"1.0"` |
+| `entity_slug` present | missing or empty string |
+| `artifact_type` present | missing or not in allowed set |
+| `environments` present | missing, empty array, or contains unknown value |
+| `status` present | missing or not in allowed set |
+| At least one surface section | no `<!-- SURFACE: -->` markers found |
+| `watch_paths` non-empty | surface section has no `watch_paths` entries |
+
+---
+
+## Consumer Skills
+
+### `rdc:deploy`
+
+Reads PUBLISH.md during the deploy pre-flight step:
+
+1. Locates `PUBLISH.md` in the app's `source_dir`.
+2. Parses YAML frontmatter — fails deploy if invalid.
+3. Unions all `watch_paths` across surface sections.
+4. Updates `app_deployments.watch_paths` with the union.
+5. After a successful deploy, calls `storeArtifact` (INSERT into `artifact_registry`) for each surface section.
+
+If `PUBLISH.md` is absent, `rdc:deploy` skips steps 2–5 and proceeds with the deploy without watch-path derivation.
+
+### `rdc:release`
+
+Reads PUBLISH.md during the promotion pre-flight gate:
+
+1. Locates `PUBLISH.md` in the app's `source_dir`.
+2. Checks `status` field — blocks promotion if `status != "active"`.
+3. Checks `environments` array — blocks promotion if `prod` is not declared.
+4. If checks pass, proceeds with Coolify promotion.
+
+### `rdc:plan`
+
+When scaffolding a new app, reads the `PUBLISH.md.template` from
+`scaffold/templates/` and hydrates it with the app's metadata to produce
+a starter `PUBLISH.md` in the new app directory.
+
+---
+
+## Example PUBLISH.md — baru-website
+
+```markdown
+---
+schema_version: "1.0"
+entity_slug: baru-website
+artifact_type: website
+environments: [dev]
+status: active
+notes: "Baru.dev — reference implementation for PUBLISH.md convention"
+---
+
+# baru-website
+
+<!-- SURFACE:website -->
+path: /
+source_dir: apps/baru-website
+build_type: nextjs
+visibility: public
+cache: no-store
+watch_paths:
+  - apps/baru-website/**
+  - packages/ui/**
+  - packages/supabase/**
+<!-- /SURFACE:website -->
+```
+
+---
+
+## Example PUBLISH.md — regen-media MCP server
+
+```markdown
+---
+schema_version: "1.0"
+entity_slug: regen-media
+artifact_type: mcp-server
+environments: [dev, prod]
+status: active
+notes: "Regen Media MCP — R2 image library, Flux/MJ generation, embeddings"
+---
+
+# regen-media
+
+<!-- SURFACE:mcp -->
+path: /mcp
+source_dir: mcp-servers/regen-media
+build_type: docker
+visibility: internal
+cache: no-store
+watch_paths:
+  - mcp-servers/regen-media/**
+<!-- /SURFACE:mcp -->
+
+<!-- SURFACE:api -->
+path: /api
+source_dir: mcp-servers/regen-media
+build_type: docker
+visibility: private
+cache: no-store
+watch_paths:
+  - mcp-servers/regen-media/**
+<!-- /SURFACE:api -->
+```
+
+---
+
+## Changelog
+
+| Version | Date | Change |
+|---------|------|--------|
+| 1.0 | 2026-05-22 | Initial spec — OQ-1/OQ-2/OQ-3 resolved; Option A Full Rollout approved |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.38",
+  "version": "0.11.0",
   "description": "RDC typed-agent dispatch skill suite for Claude Code - plan, build, review, overnight builds",
   "keywords": [
     "claude-code",
@@ -19,7 +19,7 @@
     "type": "plugin",
     "skills": "skills/",
     "guides": "guides/",
-    "version": "0.9.38",
+    "version": "0.10.0",
     "commands": "commands/"
   },
   "bin": {
@@ -32,6 +32,10 @@
     "uninstall:unix": "bash scripts/uninstall.sh",
     "validate": "node tests/validate-skills.js",
     "rdc-design": "node scripts/rdc-design-cli.mjs",
-    "test:hooks": "node scripts/test-rdc-hooks.mjs"
+    "test:hooks": "node scripts/test-rdc-hooks.mjs",
+    "prepack": "node scripts/validate-publish-manifests.js --mode warn || true && node scripts/validate-place-histories.js --mode warn || true"
+  },
+  "devDependencies": {
+    "yaml": "^2.9.0"
   }
 }

package/scaffold/templates/HISTORY.md.template

@@ -0,0 +1,39 @@
+---
+schema_version: "1.0"
+prt_slug: "PRT_SLUG"
+project_type: PROJECT_TYPE
+location:
+  county: LOCATION_COUNTY
+  state: LOCATION_STATE
+  country: LOCATION_COUNTRY
+  parcel_apn: PARCEL_APN
+  area_acres: AREA_ACRES
+  centroid: [LAT, LNG]
+acquired: "ACQUIRED_DATE"
+steward: STEWARD_NAME
+research_status: draft
+last_reviewed: "LAST_REVIEWED_DATE"
+contributors: []
+---
+
+> This is a draft stub. Research pending. Status will be promoted to in-research once primary sources are identified.
+
+## Land lineage
+
+TODO: Research land lineage of PROJECT_NAME. Cover indigenous stewardship, land grants, ownership transitions, and government survey references (PLSS township/range/section).
+
+## Stewardship transitions
+
+TODO: Document major ownership and use transitions for PROJECT_NAME from earliest recorded title to present. Include conservation easements, deed restrictions, and use-change inflection points.
+
+## Ecological context
+
+TODO: Document the ecoregion, watershed, soil classifications (NRCS Web Soil Survey), vegetation communities, water resources, wildlife corridors, and fire history for PROJECT_NAME.
+
+## Cultural significance
+
+TODO: Research indigenous place names and cultural associations, historic structures, archaeological sites, community significance (grazing allotments, water rights, access traditions), and scenic values for PROJECT_NAME.
+
+## Regulatory record
+
+TODO: Document zoning, conservation easements, water rights adjudications, federal and state permits, tax status, and any open title or lien issues of record for PROJECT_NAME.

package/scaffold/templates/PUBLISH.md.template

@@ -0,0 +1,21 @@
+---
+schema_version: "1.0"
+entity_slug: "ENTITY_SLUG"
+artifact_type: "ARTIFACT_TYPE"
+environments: [dev]
+status: draft
+notes: ""
+---
+
+# ENTITY_SLUG
+
+<!-- SURFACE:website -->
+path: /
+source_dir: SOURCE_DIR
+build_type: BUILD_TYPE
+visibility: public
+cache: no-store
+watch_paths:
+  - SOURCE_DIR/**
+  - packages/ui/**
+<!-- /SURFACE:website -->