What changed — and why.
Every meaningful change to this project has a plain-language record: what the problem was, why the decision was made, and who confirmed it. No technical background required to understand it.
Confirmed changes
These changes have been reviewed by the engineer who made them. The "why" below is their own words, confirmed at the moment the work was finished.
Hero "View resolution log" button made visible
The "View resolution log" button on the home page was invisible — it had no outline or background, so it looked like a line of grey text rather than something you could click. Anyone landing on the home page would see the purple "How it works" button and miss the resolution log entirely. The fix gives the button a subtle border so both options in the hero are clearly recognisable as interactive, while the resolution log link stays visually quieter than the primary action beside it.
How it works in practice
Three documents, one workflow. Below is a real example of each — the bug ticket, the fix spec, and the final resolution record shown from both perspectives.
Bug ticket
Describes the visible problem in plain language. No solution prescribed.
Fix spec
Describes what "done" looks like — acceptance criteria, not implementation.
Agent fixes + documents
Reads both files, finds the root cause, applies the fix, drafts the record.
Human confirms why
One sentence. Status set to confirmed. Record committed permanently.
# Fix Spec — Hero ghost button visibility
## What needs to happen
The "View resolution log →" element in the hero must look like a button.
Read docs/task-problem.md for the full description.
Look at .btn-ghost in src/pages/index.astro and figure out why the element
has no visible shape at rest. Apply the minimal fix that makes it clearly
recognisable without competing with the primary button beside it.
## Acceptance criteria
- "View resolution log →" has a visible shape at rest
- It remains less prominent than the filled "How it works" button
- No other elements on the page are affected
- npm run build completes with no errorsHero "View resolution log" button made visible
The "View resolution log" button on the home page was invisible — it had no outline or background, so it looked like a line of grey text rather than something you could click. Anyone landing on the home page would see the purple "How it works" button and miss the resolution log entirely. The fix gives the button a subtle border so both options in the hero are clearly recognisable as interactive, while the resolution log link stays visually quieter than the primary action beside it.
---
work_item: ""
pr: ""
status: confirmed
author: Leo Moura
date: 2026-06-04
---
# Hero "View resolution log" button made visible
## What changed
The `.btn-ghost` rule in `src/pages/index.astro` — one border property
added using an existing design token (`var(--border-2)`).
## How it was done
A single `border: 1px solid var(--border-2)` declaration was added to the
existing rule. The token matches card outlines used elsewhere on the page,
so the button fits the design language without introducing anything new.
## Technical result
The element now has a visible 1px outline at rest.
Static build completes with no errors.
## Why / what-for <!-- confirmed -->
The "View resolution log" button on the home page was invisible — it had no
outline or background, so it looked like a line of grey text rather than
something you could click. Anyone landing on the home page would see the
purple "How it works" button and miss the resolution log entirely. The fix
gives the button a subtle border so both options in the hero are clearly
recognisable as interactive.Create your first record
This project ships with a deliberate bug, a ticket, and a fix spec. Ask the agent to fix it — the resolution record writes itself.
Read the bug ticket in docs/task-problem.md and the fix spec in
docs/fix-spec.md. Find and fix the issue in the code. Then write
the resolution record following the agent instructions in README.md.