trail.venturanomadica.com

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

## Operating Rules

- Act only as Developer for this run. Execute the run artifacts; do not change scope or planning artifacts.
- Read only the files explicitly listed in `dev-prompt.md`.
- Do not read `trail/intents/intent-003/intent.md`, `trail/meta/trail.md`, `trail/meta/global-operating-instructions.md`, `trail/intents/intent-003/manager-instructions.md`, `trail/intents/intent-003/operating-instructions-override.md`, or any other policy/scope file outside this run folder.
- Do not write to or modify `../trail-framework/`.
- Do only what is explicitly required by this run. Do not refactor, clean up, or expand beyond the Brushy case study page and the Brushy card on `case-studies.php`.
- If ambiguity exists, choose the simplest interpretation consistent with this run, record the choice in `results.md`, and continue.
- If blocked and unable to proceed without inventing scope, stop and document the blocker in `results.md`.
- Record decisions, assumptions, deviations, and validation results in `results.md`, not in chat.

## Run-Specific Constraints

- Preserve the existing site visual language. Reuse the established Docs two-column pattern and existing site tokens before introducing any new Brushy-specific styles.
- Keep the ADF artifact viewer constrained to files inside `case-studies/brushy/adf/`. Do not implement any file-loading behavior that can read paths outside that directory.
- Render artifact contents as raw, escaped Markdown inside a syntax-highlighted code block. Do not convert the ADF files into HTML documentation.
- Keep the ADF naming distinction visible. `ai-instructions.md` must use a Changelog destination for "What's this?"; the other artifact files must use the Glossary destination.
- The intent assumes highlight.js is already loaded, but the current site does not contain an existing highlight.js include. Add the smallest scoped implementation needed for this page if syntax highlighting would otherwise not work.
- Prefer page-local changes over shared include changes. Do not modify `header.php` or `footer.php` unless there is no narrower way to satisfy the run.
- Keep all non-Brushy case study cards unchanged.