Distinguish monitoring continuity, Deliberate disable, and quitting #63

New Issue

2026-09-10T07:27:59Z

xavierk commented

2026-09-10 07:27:59 +00:00

Parent

Implement dashboard clarity and release notes

What to build

Make three different facts unmistakable: whether monitoring persists across reboots, whether a Deliberate disable has paused monitoring, and how to leave the TUI without changing monitoring. Deliver identical monitoring wording through the TUI and CLI, the distinct quit affordance, tests across both surfaces, and the corresponding README dashboard instructions.

Acceptance criteria

DC-2: A labelled CONTINUITY row in the service strip and the matching fenris status line use monitoring: active in background · persists across reboots for active plus boot-enabled, and monitoring: does not start on next boot for boot-disabled. Report the boot fact independently of run state, including while paused; retain existing separate service facts.
DC-3: A Deliberate disable produces a full-width, high-contrast paused block titled monitoring: paused — deliberate disable, with subline paused time is excluded from your usage habit · resume: fenris monitor resume. CLI status prints those same two lines. Do not equate an arbitrary systemd stop or disable with a Deliberate disable.
DC-4 and amended TUI-4: A prominent bordered q QUIT TUI rail is visually separate from monitoring state. The footer reads p pause · r resume · c collect · d disclosures, with no quit entry. Pause still confirms, resume does not, and other action semantics are unchanged.
Quitting exits only the TUI: no privileged monitoring command, timer mutation, or monitoring-period mutation occurs. Prove this for both active and paused monitoring rather than assuming monitoring is always active when quitting.
Define parity wording once in the existing status composition layer and consume it from both views; any local extraction needed to make that easy lands within this complete slice. Preserve locked em-dash and middle-dot typography; compare the lowercase parity source wording, with display capitalization treated as styling.
Extend the existing synthetic-store CI-2 parity sweep and status-render tests for active/boot-enabled, boot-disabled, and paused presentations. Headless Pilot tests verify the visible rail/footer and quit behavior. Keep CI-2/CI-4 criterion text unchanged and their surrounding regression coverage passing.
Add the continuity and paused-versus-quit instructions from the locked README “Reading the dashboard” section after the CLI reference. Coordinate authentication and release-pointer text with their owning slices; the completed section matches the companion specification without claiming unfinished sibling behavior is available.
No projection, collection, observation-store schema, or sanctioned-toggle lifecycle changes. Preserve the existing Panes layout beyond these additions.
Respect entries-at-fix-time release discipline: include a user-facing changelog entry when the shared convention exists; otherwise supply the entry with the change for incorporation by the release-notes slice, without making that slice a blocker.

Blocked by

None (can start immediately).

## Parent [Implement dashboard clarity and release notes](https://git.bongbetic.com/xavierk/Fenris/issues/61) ## What to build Make three different facts unmistakable: whether monitoring persists across reboots, whether a Deliberate disable has paused monitoring, and how to leave the TUI without changing monitoring. Deliver identical monitoring wording through the TUI and CLI, the distinct quit affordance, tests across both surfaces, and the corresponding README dashboard instructions. ## Acceptance criteria - [ ] DC-2: A labelled CONTINUITY row in the service strip and the matching `fenris status` line use `monitoring: active in background · persists across reboots` for active plus boot-enabled, and `monitoring: does not start on next boot` for boot-disabled. Report the boot fact independently of run state, including while paused; retain existing separate service facts. - [ ] DC-3: A Deliberate disable produces a full-width, high-contrast paused block titled `monitoring: paused — deliberate disable`, with subline `paused time is excluded from your usage habit · resume: fenris monitor resume`. CLI status prints those same two lines. Do not equate an arbitrary systemd stop or disable with a Deliberate disable. - [ ] DC-4 and amended TUI-4: A prominent bordered `q QUIT TUI` rail is visually separate from monitoring state. The footer reads `p pause · r resume · c collect · d disclosures`, with no quit entry. Pause still confirms, resume does not, and other action semantics are unchanged. - [ ] Quitting exits only the TUI: no privileged monitoring command, timer mutation, or monitoring-period mutation occurs. Prove this for both active and paused monitoring rather than assuming monitoring is always active when quitting. - [ ] Define parity wording once in the existing status composition layer and consume it from both views; any local extraction needed to make that easy lands within this complete slice. Preserve locked em-dash and middle-dot typography; compare the lowercase parity source wording, with display capitalization treated as styling. - [ ] Extend the existing synthetic-store CI-2 parity sweep and status-render tests for active/boot-enabled, boot-disabled, and paused presentations. Headless Pilot tests verify the visible rail/footer and quit behavior. Keep CI-2/CI-4 criterion text unchanged and their surrounding regression coverage passing. - [ ] Add the continuity and paused-versus-quit instructions from the locked README “Reading the dashboard” section after the CLI reference. Coordinate authentication and release-pointer text with their owning slices; the completed section matches the companion specification without claiming unfinished sibling behavior is available. - [ ] No projection, collection, observation-store schema, or sanctioned-toggle lifecycle changes. Preserve the existing Panes layout beyond these additions. - [ ] Respect entries-at-fix-time release discipline: include a user-facing changelog entry when the shared convention exists; otherwise supply the entry with the change for incorporation by the release-notes slice, without making that slice a blocker. ## Blocked by None (can start immediately).

xavierk added the ready-for-agent label 2026-09-10 07:27:59 +00:00

xavierk self-assigned this 2026-09-10 13:47:59 +00:00

xavierk commented

2026-09-10 14:13:56 +00:00

Implemented in d01df64. Added shared continuity and Deliberate-disable wording across CLI/TUI, a distinct quit rail, small-terminal keyboard access, README guidance, CI-2 parity, and active/paused quit non-mutation coverage. Validation: 392 passed, 34 skipped. Advisor review approved. Proposed Unreleased entry for #64: Clarify monitoring continuity, deliberate pauses, and quitting in the dashboard and status output.

Implemented in d01df64. Added shared continuity and Deliberate-disable wording across CLI/TUI, a distinct quit rail, small-terminal keyboard access, README guidance, CI-2 parity, and active/paused quit non-mutation coverage. Validation: 392 passed, 34 skipped. Advisor review approved. Proposed Unreleased entry for #64: Clarify monitoring continuity, deliberate pauses, and quitting in the dashboard and status output.

xavierk closed this issue

2026-09-10 14:13:57 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: xavierk/Fenris#63