# 84 — Back navigation on detail pages

## Goal

Audit detail routes lacking back affordances and add a shared header/back pattern consistently.

## Why

Individual plant pages (and other detail routes) have no in-page "back" except global nav.

## Depends on

- Existing app routes under `src/app/`

## Scope

- Audit all routes in `src/app/` for detail pages missing back; list them in the PR description.
- Shared back affordance (header/back component).
- Apply consistently to plant, note, list, and other detail pages.
- Playwright: `tests/e2e/navigation.spec.ts` or per-module — Back visible and returns to parent.

## Out of scope

- Redesigning global nav or dashboard tabs.

## Acceptance criteria

- [ ] Audit list included in PR.
- [ ] Shared back control on detail pages.
- [ ] E2E covers representative detail routes.

## Notes

- Gitea: [ginnoir/famapp#6](https://gitea.ginnoir.com/ginnoir/famapp/issues/6)