An implementation-ready specification — docs/spec/dashboard-clarity.md plus new criteria appended to the acceptance-criteria register — handing off five dashboard clarity additions: Fenris name and Bongbetic branding visible in the TUI, a persistence line (background + survives reboots) rendered by both TUI and fenris status, distinct quit-TUI and monitoring-paused indicators, a polkit-accurate auth banner at TUI launch, and a changelog-driven release-notes mechanism with README instructions. Decisions and spec only; no code changes in this effort.
Notes
Domain: Fenris Panes TUI (Textual), CLI fenris status, Gitea release workflow (release.yml). Skills: every decision ticket calls grilling + domain-modeling; the mockup ticket calls prototype. Standing constraints: TUI/CLI wording parity is binding (acceptance CI-2); elevation wording must be polkit-accurate — never "sudo" (sudo belongs to install/upgrade docs); CONTEXT.md glossary governs (Deliberate disable, Monitoring period); docs/spec/fenris-redesign.md is frozen — companion spec only, criteria appended to the register.
Decisions so far
Prototype the dashboard clarity additions: Quiet integration base; strong paused-state block; labelled quit and continuity treatments; subdued auth notice and Bongbetic credit.
Specify the changelog and release-notes mechanism: Keep a Changelog format; extractor fails closed (missing section, bad date, tag mismatch); release body = section + standing footer, patched on re-run; entries land at fix time; no backfill.
Assemble the dashboard clarity specification and close the map: docs/spec/dashboard-clarity.md assembled (five additions, verbatim strings, changelog/release-notes mechanism, README "Reading the dashboard" wording); DC-1–DC-8 appended and TUI-4 amended in the register; commit bb5bc9a. Map closed — destination reached.
Not yet specified
None — the way to the destination is clear and the destination is reached; no fog remains.
Out of scope
Executing the changes (code, tests, releases) — the destination is the spec; execution is a fresh effort after handoff.
Any TUI layout or information-architecture redesign beyond the five additions named in the Destination.
## Destination
An implementation-ready specification — docs/spec/dashboard-clarity.md plus new criteria appended to the acceptance-criteria register — handing off five dashboard clarity additions: Fenris name and Bongbetic branding visible in the TUI, a persistence line (background + survives reboots) rendered by both TUI and fenris status, distinct quit-TUI and monitoring-paused indicators, a polkit-accurate auth banner at TUI launch, and a changelog-driven release-notes mechanism with README instructions. Decisions and spec only; no code changes in this effort.
## Notes
Domain: Fenris Panes TUI (Textual), CLI fenris status, Gitea release workflow (release.yml). Skills: every decision ticket calls grilling + domain-modeling; the mockup ticket calls prototype. Standing constraints: TUI/CLI wording parity is binding (acceptance CI-2); elevation wording must be polkit-accurate — never "sudo" (sudo belongs to install/upgrade docs); CONTEXT.md glossary governs (Deliberate disable, Monitoring period); docs/spec/fenris-redesign.md is frozen — companion spec only, criteria appended to the register.
## Decisions so far
- [Prototype the dashboard clarity additions](https://git.bongbetic.com/xavierk/Fenris/issues/56): Quiet integration base; strong paused-state block; labelled quit and continuity treatments; subdued auth notice and Bongbetic credit.
- [Lock the dashboard wording strings](https://git.bongbetic.com/xavierk/Fenris/issues/57): verbatim strings locked (header, credit, continuity, paused banner, quit rail, auth banner); em-dash/middle-dot typography; CI-2 sweeps compare lowercase source strings; auth banner TUI-only transient.
- [Specify the changelog and release-notes mechanism](https://git.bongbetic.com/xavierk/Fenris/issues/58): Keep a Changelog format; extractor fails closed (missing section, bad date, tag mismatch); release body = section + standing footer, patched on re-run; entries land at fix time; no backfill.
- [Write the dashboard clarity acceptance criteria](https://git.bongbetic.com/xavierk/Fenris/issues/59): DC-1–DC-8 locked — branding, continuity/paused parity strings, quit rail vs Deliberate-disable block, transient polkit banner, KaC changelog + fail-closed extractor, release body assembly; TUI-4 amendment + register append deferred to [Assemble the dashboard clarity specification and close the map](https://git.bongbetic.com/xavierk/Fenris/issues/60).
- [Assemble the dashboard clarity specification and close the map](https://git.bongbetic.com/xavierk/Fenris/issues/60): docs/spec/dashboard-clarity.md assembled (five additions, verbatim strings, changelog/release-notes mechanism, README "Reading the dashboard" wording); DC-1–DC-8 appended and TUI-4 amended in the register; commit bb5bc9a. Map closed — destination reached.
## Not yet specified
- None — the way to the destination is clear and the destination is reached; no fog remains.
## Out of scope
- Executing the changes (code, tests, releases) — the destination is the spec; execution is a fresh effort after handoff.
- Any TUI layout or information-architecture redesign beyond the five additions named in the Destination.
xavierk
added this to the Wayfinder: Chart Fenris dashboard clarity milestone 2026-09-10 05:12:14 +00:00
Handoff: docs/spec/dashboard-clarity.md + the DC-1–DC-8 section (and TUI-4 amendment) in docs/spec/acceptance-criteria.md, commit bb5bc9a on main. No fog remains; execution is a fresh follow-on effort, out of scope here.
Map closed — destination reached.
All five child tickets resolved: [Prototype the dashboard clarity additions](https://git.bongbetic.com/xavierk/Fenris/issues/56) → [Lock the dashboard wording strings](https://git.bongbetic.com/xavierk/Fenris/issues/57) → [Specify the changelog and release-notes mechanism](https://git.bongbetic.com/xavierk/Fenris/issues/58) → [Write the dashboard clarity acceptance criteria](https://git.bongbetic.com/xavierk/Fenris/issues/59) → [Assemble the dashboard clarity specification and close the map](https://git.bongbetic.com/xavierk/Fenris/issues/60).
Handoff: **docs/spec/dashboard-clarity.md** + the DC-1–DC-8 section (and TUI-4 amendment) in **docs/spec/acceptance-criteria.md**, commit `bb5bc9a` on main. No fog remains; execution is a fresh follow-on effort, out of scope here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Destination
An implementation-ready specification — docs/spec/dashboard-clarity.md plus new criteria appended to the acceptance-criteria register — handing off five dashboard clarity additions: Fenris name and Bongbetic branding visible in the TUI, a persistence line (background + survives reboots) rendered by both TUI and fenris status, distinct quit-TUI and monitoring-paused indicators, a polkit-accurate auth banner at TUI launch, and a changelog-driven release-notes mechanism with README instructions. Decisions and spec only; no code changes in this effort.
Notes
Domain: Fenris Panes TUI (Textual), CLI fenris status, Gitea release workflow (release.yml). Skills: every decision ticket calls grilling + domain-modeling; the mockup ticket calls prototype. Standing constraints: TUI/CLI wording parity is binding (acceptance CI-2); elevation wording must be polkit-accurate — never "sudo" (sudo belongs to install/upgrade docs); CONTEXT.md glossary governs (Deliberate disable, Monitoring period); docs/spec/fenris-redesign.md is frozen — companion spec only, criteria appended to the register.
Decisions so far
Prototype the dashboard clarity additions: Quiet integration base; strong paused-state block; labelled quit and continuity treatments; subdued auth notice and Bongbetic credit.
Lock the dashboard wording strings: verbatim strings locked (header, credit, continuity, paused banner, quit rail, auth banner); em-dash/middle-dot typography; CI-2 sweeps compare lowercase source strings; auth banner TUI-only transient.
Specify the changelog and release-notes mechanism: Keep a Changelog format; extractor fails closed (missing section, bad date, tag mismatch); release body = section + standing footer, patched on re-run; entries land at fix time; no backfill.
Write the dashboard clarity acceptance criteria: DC-1–DC-8 locked — branding, continuity/paused parity strings, quit rail vs Deliberate-disable block, transient polkit banner, KaC changelog + fail-closed extractor, release body assembly; TUI-4 amendment + register append deferred to Assemble the dashboard clarity specification and close the map.
Assemble the dashboard clarity specification and close the map: docs/spec/dashboard-clarity.md assembled (five additions, verbatim strings, changelog/release-notes mechanism, README "Reading the dashboard" wording); DC-1–DC-8 appended and TUI-4 amended in the register; commit
bb5bc9a. Map closed — destination reached.Not yet specified
Out of scope
Map closed — destination reached.
All five child tickets resolved: Prototype the dashboard clarity additions → Lock the dashboard wording strings → Specify the changelog and release-notes mechanism → Write the dashboard clarity acceptance criteria → Assemble the dashboard clarity specification and close the map.
Handoff: docs/spec/dashboard-clarity.md + the DC-1–DC-8 section (and TUI-4 amendment) in docs/spec/acceptance-criteria.md, commit
bb5bc9aon main. No fog remains; execution is a fresh follow-on effort, out of scope here.