trail.venturanomadica.com

# Run: run-2026-03-25-20-03-17
# Purpose: Build the Brushy case study page and publish its landing-page link

## Task CS-001

**Description:** Create the `case-studies/brushy/brushy.php` page scaffold using the shared site header/footer, the established two-column Docs layout, and a safe request model for switching between the brief view and the artifact viewer.

**Inputs:**
- `header.php`
- `footer.php`
- `style.css`
- `docs/index.php`
- `case-studies/brushy/adf/`

**Outputs:**
- `case-studies/brushy/brushy.php`

**Acceptance Criteria:**
- The page includes `header.php` and `footer.php`.
- The default page state is the Brushy brief.
- The page supports selecting only the seven declared ADF files for viewing.
- Any invalid or out-of-bounds file selection is rejected without reading outside `case-studies/brushy/adf/`.
- The layout uses the existing Docs pattern as the structural baseline.

## Task CS-002

**Description:** Implement the left sidebar and artifact viewer behavior in `case-studies/brushy/brushy.php`, including the ADF note, clickable file tree, per-file "What's this?" links, viewer header, back control, and raw Markdown code rendering with syntax highlighting.

**Inputs:**
- `case-studies/brushy/adf/meta/ai-instructions.md`
- `case-studies/brushy/adf/meta/intent.md`
- `case-studies/brushy/adf/meta/manager-instructions.md`
- `case-studies/brushy/adf/runs/active/run-2026-02-01-20-44-50/ai-instructions.md`
- `case-studies/brushy/adf/runs/active/run-2026-02-01-20-44-50/dev-prompt.md`
- `case-studies/brushy/adf/runs/active/run-2026-02-01-20-44-50/results.md`
- `case-studies/brushy/adf/runs/active/run-2026-02-01-20-44-50/tasks.md`

**Outputs:**
- `case-studies/brushy/brushy.php`

**Acceptance Criteria:**
- The sidebar shows the declared ADF tree and all seven files.
- Clicking each file swaps the brief view for the file viewer.
- The viewer header shows both the file name and its full ADF path.
- The viewer contains a back control that returns to the Brushy brief.
- `ai-instructions.md` links to `/docs/?page=changelog`; all other viewer/sidebar "What's this?" links point to `/docs/?page=glossary`.
- Artifact contents are escaped and rendered inside a Markdown-highlighted code block.
- Syntax highlighting works, with page-local setup added if the site does not already provide it.

## Task CS-003

**Description:** Complete the Brushy brief view with the exact provided product copy, the required stats grid values, the YouTube demo embed, and the six portrait screenshots. Add only the minimum styling needed to make the case study page fit the existing site system on desktop and mobile.

**Inputs:**
- `trail/meta/files/trail-style-guide.html`
- `style.css`
- `case-studies/brushy/media/01-brushy-timer.png`
- `case-studies/brushy/media/02-brushy-in-progress.png`
- `case-studies/brushy/media/03-brushy-brushing-complete.png`
- `case-studies/brushy/media/04-brushy-toothbrush-info.png`
- `case-studies/brushy/media/05-brushy-calendar.png`
- `case-studies/brushy/media/06-brushy-settings.png`

**Outputs:**
- `case-studies/brushy/brushy.php`
- `style.css` if additional scoped styles are required

**Acceptance Criteria:**
- The default main panel shows the exact supplied Brushy description without copy changes.
- The stats display the required values: `1`, `3 hours`, `15 minutes`, `30 minutes`, `30 minutes`.
- The YouTube video is embedded and playable from the case study page.
- All six screenshots are visible in the brief view.
- Any new styling is consistent with the site stylesheet and does not disturb unrelated pages.
- The layout remains usable on mobile after any style additions.

## Task CS-004

**Description:** Update the Brushy card in `case-studies.php` from "Coming Soon" to a live link to `case-studies/brushy/brushy.php`, while leaving every other case study card untouched.

**Inputs:**
- `case-studies.php`

**Outputs:**
- `case-studies.php`

**Acceptance Criteria:**
- The Brushy card no longer shows the "Coming Soon" badge.
- The Brushy card title and/or card body links to `case-studies/brushy/brushy.php`.
- The Brushy card includes a one-line description.
- No other case study card content or behavior changes.

## Task CS-005

**Description:** Validate the run outputs and document the execution record in `results.md`.

**Inputs:**
- `case-studies/brushy/brushy.php`
- `case-studies.php`
- `style.css` if modified

**Outputs:**
- `results.md`

**Acceptance Criteria:**
- Validation covers PHP syntax for each modified PHP file.
- Validation confirms the page-level requirements were implemented, including the seven-file sidebar, brief/viewer switching, correct "What's this?" destinations, safe file serving behavior, media presence, and Brushy card link.
- `results.md` is populated with completed tasks, files changed/added, deviations, assumptions, notable observations, and any blockers or open questions.