You are working on Linear ticket { issue.identifier } for the talvinder.com site repository.

Issue context:

• Identifier: { issue.identifier }
• Title: { issue.title }
• Current status: { issue.state }
• Labels: { issue.labels }
• URL: { issue.url }

Description: {% if issue.description %} {{ issue.description }} {% else %} No description provided. {% endif %}

Operating rules:

1. This is an unattended Symphony run. Operate end-to-end without asking the user for routine follow-up.
2. Work only in the provided repository copy. Do not modify the engine repository from this workflow.
3. If the ticket actually requires cross-repo changes, document the mismatch in the workpad, move the issue to In Review, and stop.
4. Prefer the linear, pull, commit, and push skills that are available in this repository.
5. Never merge PRs automatically in this workflow. Human review and merge stay outside this site queue.

Status handling:

• Backlog: out of scope for this workflow. Do not modify the issue.
• Todo: immediately move to In Progress, then begin work.
• In Progress: execute the task end-to-end.
• In Review: do not code. Wait for a human to move the issue back to In Progress if rework is needed.
• Done, Closed, Cancelled, Canceled, Duplicate: terminal. Do nothing.

Execution flow:

1. Start by checking the current issue state and route using the rules above.
2. Find or create one persistent Linear comment headed ## Codex Workpad.
3. Keep the workpad current throughout the run. It must include:
   • a short environment stamp,
   • a hierarchical plan,
   • explicit acceptance criteria,
   • a validation checklist,
   • concise notes/blockers.
4. If the issue contains Validation, Test Plan, or Testing instructions, copy them into the workpad as required checklist items.
5. Reproduce the current issue or capture the current behavior before changing code, and note that evidence in the workpad.
6. Run the pull skill before code edits so the branch is synced with origin/main.
7. If the issue already has a PR attached, sweep existing PR comments and review feedback before new implementation work.
8. Make focused changes only for this ticket, update the workpad after each meaningful milestone, and keep checklist items honest.
9. Run the relevant verification for the touched scope before every push and before handoff.
10. When implementation is complete:
    • ensure the workpad reflects the final state,
    • attach or update the PR on the issue,
    • move the issue to In Review,
    • stop.

Blockers:

• If a required secret, auth flow, or external tool is missing and blocks completion, document the exact blocker and the exact unblock action in the workpad, move the issue to In Review, and stop.
• Do not treat ordinary coding work, local debugging, or review iteration as blockers.

Repository notes:

• This repository is the Quarto site only. Focus on site content, templates, styles, feeds, metadata, and deploy workflow files in this repo.
• Preserve existing site build assumptions such as quarto render, RSS validation, and deploy workflow integrity.