@schandlergarcia/sf-web-components 2.1.0 → 2.2.1

package/.a4drules/features/command-center-dashboard-rule.md

@@ -15,12 +15,12 @@ These rules apply to all dashboard files.
 After creating a dashboard, you MUST update all 3 files or the dashboard will never appear:
 
 1. **`CommandCenter.tsx`** — import and render your dashboard (change only the import line)
-2. **`Home.tsx`** — REWRITE to render `CommandCenter` (it ships as Account Search by default):
+2. **`Home.tsx`** — rewrite to render `CommandCenter` (it ships as Account Search by default):
    ```tsx
    import CommandCenter from "@/components/workspace/CommandCenter";
    export default function HomePage() { return <CommandCenter />; }
    ```
-3. **`routes.tsx`** — set `Home` as index route with label "Dashboard", move Search to `/search`
+3. **`routes.tsx`** — set `Home` as index route with label "Dashboard"
 
 **If you skip this, the user sees the Account Search page instead of your dashboard.**
 

package/.a4drules/features/pre-code-checklist.md

@@ -29,9 +29,9 @@ Read `.a4drules/skills/command-center-builder/SKILL.md` before building. It has
   // ... render <MyDashboard /> inside the existing providers
   ```
 
-- [ ] **`Home.tsx`** — REPLACE the entire file (it ships as Account Search by default):
+- [ ] **`Home.tsx`** — rewrite the entire file (it ships as Account Search by default):
   ```tsx
-  // src/pages/Home.tsx — REPLACE EVERYTHING
+  // src/pages/Home.tsx
   import CommandCenter from "@/components/workspace/CommandCenter";
   export default function HomePage() {
     return <CommandCenter />;

package/.a4drules/skills/command-center-builder/SKILL.md

@@ -12,23 +12,23 @@ description: >-
 
 These rules apply when building dashboards rendered by `CommandCenter.tsx`. For full component API details, read the **component-library** skill.
 
-> **BUILD GUIDE:** The dashboard is built in 3 phases. Read [`getting-started.md`](getting-started.md) for what to build (and what to skip) in each phase. Do NOT build ahead — only build what the current phase asks for.
+> **BUILD GUIDE:** Read [`getting-started.md`](getting-started.md) for the full step-by-step process.
 
-## WIRING — DO THIS FIRST (before building the dashboard)
+## WIRING — Making Your Dashboard Visible
 
-**Building a dashboard requires updating 4 files. If you only create the dashboard file, the user will never see it — they'll see the old Account Search page instead.**
+**Building a dashboard requires updating 4 files. If you only create the dashboard file, the user will never see it — they'll see the default Account Search page instead.**
 
 Read the existing `Home.tsx`, `CommandCenter.tsx`, and `routes.tsx` BEFORE you start building. Plan all 4 file changes up front:
 
 1. `src/pages/YourDashboard.tsx` — the dashboard component
 2. `src/components/workspace/CommandCenter.tsx` — import and render your dashboard
-3. `src/pages/Home.tsx` — **MUST be rewritten** to render CommandCenter (it ships as Account Search)
+3. `src/pages/Home.tsx` — rewrite to render CommandCenter (it ships as Account Search)
 4. `src/routes.tsx` — set Home as index route with label "Dashboard"
 
 **Home.tsx ships as an Account Search page by default.** You MUST replace its entire contents:
 
 ```tsx
-// src/pages/Home.tsx — REPLACE the entire file
+// src/pages/Home.tsx
 import CommandCenter from "@/components/workspace/CommandCenter";
 
 export default function HomePage() {
@@ -60,7 +60,7 @@ export default function CommandCenter() {
 }
 ```
 
-**routes.tsx** — make Home the index route, move Search to `/search`:
+**routes.tsx** — make Home the index route with label "Dashboard":
 
 ```tsx
 {

package/.a4drules/skills/command-center-builder/getting-started.md

@@ -1,80 +1,63 @@
 # Command Center Dashboard — Build Guide
 
-The dashboard is built in **3 phases**, one per user prompt. Each phase adds a layer. Do NOT build ahead — only build what the current phase asks for.
+This guide teaches you how to build a dashboard using the Command Center component library.
 
 ---
 
-## RULES THAT APPLY TO EVERY PHASE
+## General Rules
 
-> **Read these first. Violations of these rules are the #1 cause of failed builds.**
+> **Read these first. They prevent the most common mistakes.**
 
-1. **Phase 1 writes new files. Phases 2 and 3 make surgical edits.** Never rewrite the dashboard file from scratch in Phase 2 or 3. Rewriting a 400+ line file takes 60s, risks losing prior work, and introduces regressions. Surgical edits take seconds.
+1. **Do NOT read library component source files.** Do NOT read `GeoMap.jsx`, `BaseCard.jsx`, `Avatar.jsx`, `ChatBar.jsx`, `ChartCard.jsx`, `D3Chart.jsx`, `useDataSource.jsx`, `DataModeProvider.jsx`, `DataModeToggle.jsx`, or any file inside `src/components/library/`. All props and patterns are documented in this build guide and the SKILL.md. Reading source files wastes time and produces no new information.
 
-2. **Do NOT read library component source files.** Do NOT read `GeoMap.jsx`, `BaseCard.jsx`, `Avatar.jsx`, `ChatBar.jsx`, `ChartCard.jsx`, `D3Chart.jsx`, `useDataSource.jsx`, `DataModeProvider.jsx`, `DataModeToggle.jsx`, or any file inside `src/components/library/`. All props and patterns are documented in this build guide and the SKILL.md. Reading source files wastes time and produces no new information.
+2. **Do NOT load unnecessary skills.** You only need `command-center-builder`. Do NOT load `outer-app`, `component-library`, `command-center-project`, `agentforce-test`, or `agentforce-observability` — they add latency and aren't needed.
 
-3. **Do NOT load unnecessary skills.** Phase 1 needs only `command-center-builder`. Do NOT load `outer-app`, `component-library`, `command-center-project`, `agentforce-test`, or `agentforce-observability` — they add latency and aren't needed.
+3. **Do NOT run `npm run build` or `npm run dev` during the build.** Vite handles JSX/TSX regardless of TypeScript errors. Pre-existing TS7016 errors (from untyped .jsx library files) are normal and expected.
 
-4. **Do NOT run `npm run build` or `npm run dev` during the build.** Vite handles JSX/TSX regardless of TypeScript errors. Pre-existing TS7016 errors (from untyped .jsx library files) are normal and expected.
+4. **STOP and ASK before creating Salesforce metadata.** Custom fields, platform events, and Apex classes should be suggested to the user first. Never create them proactively.
 
-5. **STOP and ASK before creating Salesforce metadata.** Custom fields, platform events, and Apex classes should be suggested to the user first. Never create them proactively.
-
-6. **Do NOT create extra files not listed in the build guide.** Each phase lists exactly which files to create or edit. Do NOT create wrapper hooks, adapter files, .env files, or any file not explicitly listed.
+5. **Do NOT create extra files not listed in this guide.** No wrapper hooks, adapter files, .env files, or any file not explicitly listed.
 
 ---
 
-## Phase 1 — Build the Dashboard (sample data only)
-
-### FORBIDDEN in Phase 1
-- ❌ ChatBar or any Agentforce/AI integration (that's Phase 3)
-- ❌ Live data hooks or live data wiring (that's Phase 2)
-- ❌ Salesforce metadata — custom fields, platform events, Apex
-- ❌ Reading library component source files
-- ❌ Loading skills other than `command-center-builder`
+## Step 1 — Create the Dashboard
 
-### Files to read
+### Files to read first
 1. Your PRD or requirements document — the full spec
 2. Your sample data file — to understand available data shapes
 
 ### Files to create/edit (in order)
 ```
-1. WRITE  src/pages/YourDashboard.tsx          ← full dashboard, one pass
+1. WRITE  src/pages/YourDashboard.tsx                ← full dashboard, one pass
 2. EDIT   src/components/workspace/CommandCenter.tsx  ← import YourDashboard
-3. WRITE  src/pages/Home.tsx                   ← REPLACE with CommandCenter wrapper (3 lines)
-4. EDIT   src/routes.tsx                       ← change index route label to "Dashboard"
+3. WRITE  src/pages/Home.tsx                         ← rewrite to render CommandCenter
+4. EDIT   src/routes.tsx                             ← change index route label to "Dashboard"
 ```
 
 ### What to build
 - Choose your layout pattern (visualization-hero with full-width map, or grid-first)
 - Pick components from the library for each section (MetricCard, ChartCard, ListCard, TableCard, etc.)
-- Wire all data via `useDataSource({ sample: SAMPLE_DATA, live: [] })` — leave `live:` empty for now
+- Wire all data via `useDataSource({ sample: SAMPLE_DATA, live: [] })` — leave `live:` empty initially
 - Add dark mode support to any custom markup
 
 ### Wiring
 - `CommandCenter.tsx` → import your dashboard instead of BlankDashboard
-- `Home.tsx` → **REPLACE** the Account Search page with a 3-line wrapper that renders `<CommandCenter />`
-- `routes.tsx` → change the index route handle to `{ showInNavigation: false, showNavBar: false, label: "Dashboard" }`
+- `Home.tsx` → rewrite to render `<CommandCenter />` (it ships as an Account Search page by default)
+- `routes.tsx` → change the index route label to "Dashboard"
 
 ### Write the dashboard in one pass
 Plan the entire file before writing. Do NOT write a partial dashboard and iterate — write the complete component with all imports, data, and JSX in a single Write call.
 
 ---
 
-## Phase 2 — Connect to Live Data
+## Step 2 — Connect to Live Data (when ready)
 
-### FORBIDDEN in Phase 2
-- ❌ Rewriting the dashboard file from scratch — make targeted surgical edits only
-- ❌ Reading library source files (`useDataSource.jsx`, `DataModeProvider.jsx`, etc.)
-- ❌ ChatBar or AI/agent integration (that's Phase 3)
-- ❌ Creating extra files not listed below
-- ❌ Running `npm run build` between edits
+When you're ready to wire live Salesforce data, make **targeted surgical edits** to the existing dashboard file. Do NOT rewrite the whole file.
 
-### The point of Phase 2
-The dashboard switches from sample data to live data from your Salesforce org. The `useDataSource` hook handles the toggle — you just need to fill in the `live:` props and flip the backend switch.
-
-### How the switch works
+### How the data switch works
 `ENABLE_SAMPLE_DATA_CACHE` in `src/lib/dataStrategy.ts` controls the mode. `CommandCenter.tsx` reads this flag and passes `initialMode` to `DataModeProvider`. When `true` (default) → sample mode. When `false` → live mode, every `useDataSource` returns its `live` prop.
 
-### Edits to make (in order)
+### Edits to make
 
 **Edit 1 — Add live data import** at the top of your dashboard file:
 ```tsx
@@ -88,9 +71,9 @@ const live = useLiveData();
 
 **Edit 3 — Update every `useDataSource` call** to pass live data:
 ```tsx
-// Before (Phase 1):
+// Before:
 const items = useDataSource({ sample: SAMPLE_ITEMS, live: [] });
-// After (Phase 2 — just fill in the live: prop):
+// After:
 const items = useDataSource({ sample: SAMPLE_ITEMS, live: live.items });
 ```
 Do this for ALL `useDataSource` calls in the dashboard.
@@ -102,30 +85,15 @@ Do this for ALL `useDataSource` calls in the dashboard.
 export const ENABLE_SAMPLE_DATA_CACHE = false;
 ```
 
-> ⚠️ **Do NOT skip Edit 5.** This is the most critical step. Without it, the data never switches. The dashboard will still show sample data no matter what you wired in Edits 1-4.
-
-That's targeted surgical edits, not a full rewrite.
+> Do NOT skip Edit 5. Without it, the data never switches.
 
 ---
 
-## Phase 3 — Add AI Assistant
+## Step 3 — Add an AI Assistant (when ready)
 
-### FORBIDDEN in Phase 3
-- ❌ `AgentforceConversationClient` — do NOT use the iframe widget. Use the Agent REST API via a dedicated hook.
-- ❌ Wrapper hooks or adapter files — use the agent hook directly.
-- ❌ `.env` or `.env.local` files — config is hardcoded in `src/config/agentApi.ts`
-- ❌ Rewriting the dashboard file from scratch
-- ❌ Reading library component source files (including `ChatBar.jsx`)
+When you're ready to add a chat assistant, make **targeted surgical edits** to the existing dashboard file.
 
-### Pre-installed files (already in the project — do NOT recreate)
-If the agent hook and config files are already installed by the package, they already exist:
-- `src/hooks/useAgentChat.ts` — the Agent API hook
-- `src/config/agentApi.ts` — endpoint config
-- `vite.config.ts` — already has proxy rules for agent API
-
-**Do NOT create, rewrite, or modify these files.** Just import and use them.
-
-### Edits to make (in order)
+### Edits to make
 
 **Edit 1 — Add imports** at the top of the dashboard file:
 ```tsx
@@ -153,7 +121,7 @@ const handleChat = (text: string) => {
 };
 ```
 
-**Edit 4 — Insert ChatBar JSX** between the visualization area and data panels:
+**Edit 4 — Insert ChatBar JSX** in a suitable location:
 ```tsx
 <div className="px-4 pt-4">
   <ChatBar
@@ -165,27 +133,14 @@ const handleChat = (text: string) => {
 </div>
 ```
 
-That's 4 targeted edits. Nothing else.
-
 ### After adding AI — suggest Salesforce metadata
 
 If your use case benefits from platform events or Apex services, suggest them to the user and wait for confirmation before creating.
 
 ---
 
-## Phase Summary
-
-| | Phase 1 | Phase 2 | Phase 3 |
-|---|---------|---------|---------|
-| Dashboard layout & panels | Write new file | — | — |
-| Sample data | Wire (`live: []`) | — | — |
-| Live data wiring | Skip | Surgical edits | — |
-| Flip `dataStrategy.ts` to `false` | Skip | **Don't skip** | — |
-| ChatBar / AI assistant | Skip | Skip | Surgical edits |
-| Agent hook | Skip | Skip | Import (pre-installed) |
-| Wrapper hooks / adapters | **NO — never** | **NO — never** | **NO — never** |
-| Salesforce metadata | Skip | Suggest → wait | Suggest → wait |
+## Data mode control
 
-**Data mode control:** `ENABLE_SAMPLE_DATA_CACHE` in `src/lib/dataStrategy.ts` is the backend switch. Phase 1 leaves it `true`. Phase 2 flips it to `false`.
+`ENABLE_SAMPLE_DATA_CACHE` in `src/lib/dataStrategy.ts` is the backend switch. Default is `true` (sample mode). Set to `false` to switch to live data.
 
-**Agent communication:** The agent hook handles OAuth → session → messages → cleanup via the Agent REST API. Config is in `src/config/agentApi.ts`. Vite proxy rules forward requests. These files are pre-installed — do NOT recreate them.
+**Agent communication:** If using an Agentforce hook, the hook handles OAuth → session → messages → cleanup via the Agent REST API. Config is in `src/config/agentApi.ts`. These files may already be pre-installed — check before creating them.

package/.a4drules/skills/command-center-builder/improved-build-process.md

@@ -1,22 +1,14 @@
 # Efficient Build Process
 
-## The #1 Rule: Phase 1 Writes, Phases 2-3 Edit
-
-- **Phase 1** creates your dashboard file from scratch (Write). Also writes CommandCenter.tsx, Home.tsx, edits routes.tsx.
-- **Phase 2** makes targeted surgical edits to wire live data. Never rewrites the file.
-- **Phase 3** makes targeted surgical edits to add AI chat. Never rewrites the file.
-
-Rewriting a 400+ line file from scratch takes 60 seconds, risks losing prior work, and can introduce regressions. Surgical edits take seconds each and preserve everything.
-
 ## Speed Rules
 
 1. **Load only `command-center-builder` skill before building.** Do NOT load component-library, command-center-project, outer-app, agentforce-test, or agentforce-observability — they add latency and aren't needed.
 
 2. **Do NOT read component source files.** This means ALL files inside `src/components/library/` are off-limits: GeoMap.jsx, BaseCard.jsx, Avatar.jsx, ChatBar.jsx, D3Chart.jsx, useDataSource.jsx, DataModeProvider.jsx, DataModeToggle.jsx, etc. Props/patterns are documented in the build guide.
 
-3. **Phase 1: Write the dashboard in one pass.** Plan the full file before writing. Write the complete component with all imports, data, and JSX in a single Write call.
+3. **Write the dashboard in one pass.** Plan the full file before writing. Write the complete component with all imports, data, and JSX in a single Write call.
 
-4. **Phases 2-3: Make the edits listed in the build guide.** Targeted surgical edits only. No full rewrites.
+4. **When editing an existing dashboard, make targeted surgical edits.** Never rewrite a 400+ line file from scratch. Rewriting takes 60s, risks losing prior work, and introduces regressions. Surgical edits take seconds.
 
 5. **Do NOT run `npm run build`, `npm run dev`, `tsc`, or `npm run validate:dashboard` during the build.** Vite handles it. TS7016 errors are pre-existing and expected.
 
@@ -24,51 +16,23 @@ Rewriting a 400+ line file from scratch takes 60 seconds, risks losing prior wor
 
 7. **Do NOT create extra files.** No wrapper hooks, no .env files, no adapter files. The build guide lists every file to create or edit.
 
-## Phase 1 File Write Order
-
-```
-1. WRITE  src/pages/YourDashboard.tsx              ← full dashboard, one pass
-2. EDIT   src/components/workspace/CommandCenter.tsx  ← swap BlankDashboard → YourDashboard
-3. WRITE  src/pages/Home.tsx                       ← 3-line CommandCenter wrapper
-4. EDIT   src/routes.tsx                           ← change index route label to "Dashboard"
-```
-
-## Phase 2 Edit Order
+## File Write Order
 
-```
-1. Add live data import to your dashboard file
-2. Add live data hook call inside the component
-3. Update each useDataSource({ sample, live: [] }) → live: live.xxx
-4. Update any derived values to react to active data
-5. Flip ENABLE_SAMPLE_DATA_CACHE to false in src/lib/dataStrategy.ts
-→ STOP — suggest metadata if applicable, wait for confirmation
-```
-
-⚠️ **The final edit (flipping the flag) is the most critical.** Without it, the data never switches.
-
-## Phase 3 Edit Order
+When building a new dashboard:
 
 ```
-1. Add ChatBar + agent hook imports to your dashboard file
-2. Add chat suggestions constant at module scope
-3. Add agent hook call + handleChat inside component
-4. Insert <ChatBar /> JSX between visualization and data panels
-→ STOP — suggest metadata if applicable, wait for confirmation
+1. WRITE  src/pages/YourDashboard.tsx                ← full dashboard, one pass
+2. EDIT   src/components/workspace/CommandCenter.tsx  ← swap BlankDashboard → YourDashboard
+3. WRITE  src/pages/Home.tsx                         ← rewrite to render CommandCenter
+4. EDIT   src/routes.tsx                             ← change index route label to "Dashboard"
 ```
 
-**Agent hook and config files are pre-installed.** Do NOT recreate them. Just import and use.
-
-**NEVER use AgentforceConversationClient.** Use the Agent REST API via the dedicated hook.
-
-**NEVER create wrapper hooks.** Use the agent hook directly.
-
 ## Common Time Wasters
 
 | Waste | Fix |
 |-------|-----|
 | Loading 4-5 skills before starting | Load only command-center-builder |
 | Reading GeoMap.jsx, ChatBar.jsx, useDataSource.js source | Props are in the build guide — trust the docs |
-| Rewriting the dashboard in Phase 2/3 | Make targeted surgical edits |
+| Rewriting the entire dashboard file to make a small change | Make targeted surgical edits |
 | Running `npm run build` between edits | Don't — Vite handles it |
 | Creating wrapper hooks or adapter files | **NEVER** — use hooks directly |
-| Creating .env or .env.local files | **NEVER** — config is hardcoded in src/config/agentApi.ts |

package/.a4drules/skills/command-center-guide/SKILL.md

@@ -12,7 +12,7 @@ description: >-
 
 ## How to Build Efficiently
 
-**Read these two files, then start building. Do not load other skills or explore component source files.**
+**Read these two things, then start building. Do not load other skills or explore component source files.**
 
 1. **`.a4drules/skills/command-center-builder/SKILL.md`** — has the wiring steps, conventions, component APIs, and everything you need
 2. **Your PRD / spec document** — the product spec (layout, data model, brand tokens)
@@ -22,14 +22,10 @@ That's it. The builder skill already contains the component API reference inline
 ## Build Order (write files in this exact order)
 
 1. **Read** the PRD and builder skill
-2. **Write** `src/pages/MyDashboard.tsx` (or your dashboard name) — the full dashboard in one pass
-3. **Write** `src/components/workspace/CommandCenter.tsx` — import your dashboard
-4. **Write** `src/pages/Home.tsx` — REPLACE with CommandCenter (it ships as Account Search):
-   ```tsx
-   import CommandCenter from "@/components/workspace/CommandCenter";
-   export default function HomePage() { return <CommandCenter />; }
-   ```
-5. **Edit** `src/routes.tsx` — set Home as index route with label "Dashboard"
+2. **Write** `src/pages/YourDashboard.tsx` — the full dashboard in one pass
+3. **Edit** `src/components/workspace/CommandCenter.tsx` — import your dashboard
+4. **Write** `src/pages/Home.tsx` — rewrite to render CommandCenter (it ships as Account Search)
+5. **Edit** `src/routes.tsx` — change index route label to "Dashboard"
 6. **Done** — do NOT run `npm run build`, `npm run dev`, or `tsc`
 
 ## Other Skills (load only when needed later)

package/.a4drules/skills/component-library/card-components.md

@@ -138,7 +138,7 @@ Status icons: `"complete"` → green check, `"working"` → spinning (indigo), `
 
 ```jsx
 <SectionCard
-  title="Eva · Agentforce Agent"
+  title="AI Assistant"
   description="Powered by Agentforce"
   label="LIVE"                      // small pill badge
   variant="default"                 // "default" | "primary" | "secondary" | "accent"

package/.a4drules/validation-requirements.md

@@ -27,14 +27,13 @@ npm run validate:dashboard
 - After updating styles
 - After changing imports
 - Before committing code
-- Before reporting a phase/task as complete
+- Before reporting a task as complete
 
 **Frequency:** If in doubt, run it. It takes <1 second.
 
 ## Zero Errors Required
 
 The validator MUST show zero errors before:
-- Proceeding to the next build phase
 - Reporting a task as complete
 - Committing code
 - Deploying
@@ -43,7 +42,6 @@ The validator MUST show zero errors before:
 - Dismiss errors as "justified" or "acceptable"
 - Skip validation "because you're sure it's correct"
 - Report work as complete with validator errors
-- Proceed to the next phase with errors
 
 **Every error has a fix.** The fix is usually switching to a library component.
 
@@ -174,12 +172,9 @@ Dashboard is ready
 
 Any other output means there are errors that MUST be fixed.
 
-## Integration with Build Phases
+## When to Validate
 
-Run the validator at the end of each build phase before proceeding to the next:
-
-- **End of each phase:** Run validator, fix all errors → proceed to next phase
-- **Final phase:** Run validator, fix all errors → DONE
+Run the validator after completing your dashboard changes. Fix all errors before reporting the task as done.
 
 ## Do Not Run These Instead
 

package/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.2.1] - 2026-04-10
+
+### Fixed
+- **Postinstall `.a4drules` path** — no longer hardcodes 5-level deep path; now walks up to find `sfdx-project.json` for SFDX projects, or falls back to cwd for standalone projects.
+- **`setup` script collision** — renamed from `setup` to `sfwc:setup` to avoid conflicts with existing project scripts (e.g., SFDX org-setup).
+
+## [2.2.0] - 2026-04-04
+
+### Added
+- **Partner Hub PRD** — `brands/engine/PARTNER_HUB_PRD.md` with full product spec for hotel partner operations dashboard including data model, attrition penalty domain, Agentforce agent config, and a new Section 10 with complete dashboard layout specification (grid wireframe, 5 KPI definitions, 8 panel definitions with component mappings).
+- **Partner Hub sample data** — `brands/engine/partner-hub-sample-data.js` with 12 hotel partners, 12 contracts, 17 invoices, 6 attrition penalties (including hero ATR-00001), 7 dispute cases, 8 activity items, pre-computed METRICS, and chart-ready arrays (tier breakdown, revenue by partner, invoice trend).
+- **`npm run setup`** — manual re-run of postinstall for projects where the postinstall hook was skipped. Added to consuming projects automatically.
+
+### Changed
+- **apply-brand.mjs** — now copies `partner-hub-sample-data.js` to `src/data/` and auto-discovers all PRD files (matching `*_PRD.md` or `*-prd.md`) in the brand directory.
+- **.a4drules** — removed all phase-based workflow language (Phase 1/2/3) from getting-started.md, improved-build-process.md, SKILL.md, validation-requirements.md, command-center-guide, command-center-dashboard-rule.md, and pre-code-checklist.md. Build guide is now a simple step-by-step (Step 1: build, Step 2: wire live data, Step 3: add AI). Restored Home.tsx rewrite as part of the wiring steps. Replaced "Eva" example with generic "AI Assistant" in card-components.md.
+
 ## [2.1.0] - 2026-04-04
 
 ### Added