docs(backlog): track activity-readability Phase 4 + 5#624
Merged
Conversation
Phases 4 (grouping/dedup/noise) and 5 (audit compliance hardening: tamper-evidence + retention + AU-control mapping) lived only in docs/engineering/activity_readability_plan.md, not in BACKLOG.md (the SSOT for pending work). Add them under Activity Feed Follow-ups, with the scheduler-tick noise + the should-ticks-be-audit-events taxonomy question captured under Phase 4. Also adds the dashboard Top-failing-hosts UUID one-liner (same no-UUIDs goal, non-activity widget).
remyluslosius
added a commit
that referenced
this pull request
Jun 21, 2026
Bumps packaging/version.env to 0.2.0-rc.12 (Eyrie) and adds the CHANGELOG entry covering the 17 PRs since rc.11 (#610-#626): - Activity & audit readability initiative (#615-#624): human-readable titles across all five feed legs, host-scoped Activity + Audit tabs, readable Settings audit rows, CSV/JSON audit export (AU-7), 'The system' attribution. - Host Management fixes (#611, #613): card scan link + working Group/Filters + server-persisted view preference; hostname/IP on scan-detail header. - Pre-release security hardening (#625, #626): CSV formula-injection + silent-truncation guards, keyset-cursor data-loss fix, bounded audit detail. Also drops the now-fixed cursor-pagination data-loss row from BACKLOG.md (resolved by #626). Release tests (changelog/version/package) green. The git tag push that triggers the signed release pipeline remains the operator's step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You asked whether Phases 4 and 5 were in the backlog — they weren't (only in
docs/engineering/activity_readability_plan.md). This adds them to BACKLOG.md (the SSOT for pending work):scheduler.tick.dispatchednoise and the coupled taxonomy question (should routine ticks be audit events at all?).signaturecolumn, AU-9), retention/archival (AU-11), AU-control mapping doc.Docs only.