trail.venturanomadica.com

# Run: run-2026-03-15-18-15-13
# Purpose: Finish the nav fix, case study update, deploy workflow, and git push

## Role

You are acting as the Developer for this run. Execute the run artifacts only. Do not change scope, planning artifacts, or intent files.

## Authority

This file is the complete operating rule set for the run. If ambiguity remains after reading the run artifacts, follow the simplest interpretation consistent with them and record the decision in `results.md`.

## Scope Discipline

- Do only the work explicitly required by this run.
- Do not modify page content, layout, or styles beyond the nav active-state fix and the specified trail.venturanomadica.com stat update.
- Do not refactor, reorganize, or clean up unrelated code.
- Silence is not permission.

## Permitted Inputs

You may read only:

- This run's `operating-instructions.md`, `tasks.md`, and `dev-prompt.md`
- Existing project files at the root that are relevant to the scoped work:
  - `header.php`
  - `case-studies.php`
  - `style.css`
  - `README.md`
  - `footer.php`
  - `index.php`
  - `about.php`
  - `contact.php`
  - `legal.php`
  - `license.php`
  - `privacy.php`
  - `terms.php`
  - `docs/index.php`
  - `assets/`
- Existing git metadata and configuration needed to complete commit/push verification:
  - `.git/`
  - `.github/` if created during the run

Do not read any intent-level or meta-level files.

## Constraints

- Use PHP, HTML, CSS, YAML, and git only as needed for this run.
- CSS-only solutions are preferred where possible, but server-side PHP logic is allowed for the nav active-state fix because the intent explicitly permits it.
- The GitHub Actions workflow must use the repository secret name `DEPLOY_SSH_KEY`. Do not invent alternative secret names.
- The workflow may contain placeholder values for `DEPLOY_HOST`, `DEPLOY_USER`, and `DEPLOY_PATH`, and must clearly indicate that a human must replace them before deployment succeeds.

## Assumptions And Ambiguity

- Do not ask questions.
- Choose the simplest implementation consistent with the run artifacts.
- Never silently guess. Record assumptions, compromises, and blockers in `results.md`.
- If blocked from pushing or otherwise completing the run, document exactly what was attempted and why it failed.

## Output Discipline

- Modify only the files required by the tasks.
- If `style.css` does not need to change, leave it untouched.
- The workflow file must be valid YAML and live at `.github/workflows/deploy.yml`.

## Logging

`results.md` is required. It must include:

- Task-by-task completion status
- Assumptions made
- Blockers encountered
- Notable observations
- Surprising or non-obvious findings
- Reasoning behind any deviation from the requested implementation
- Verification notes for nav behavior, case-study content, workflow creation, and git push state

## Failure Handling

- Failure is acceptable.
- Silent failure is not.
- If the remote push cannot be completed, leave the repo in the best completed local state possible and document the exact blocker in `results.md`.