Skip to content

net docs: document explicit diagnostics, expiry, and summary-only operations - #793

Closed
Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-default-summaryfrom
phealy/lightweight-status-operations-docs
Closed

Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-default-summaryfrom
phealy/lightweight-status-operations-docs

Conversation

@phealy

@phealy Patrick W. Healy (phealy) commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Purpose

Update operations, troubleshooting, and architecture for summary-only routine state; explicit dashboard and CLI loading; the common detail API; immediate request delivery; TTL ownership; rollback; and honest failure states.

Compatibility

Based on #792, where summary is now the publishing default. Documents node show --watch retirement, raw named-node JSON, summary-only global exports, disabled-publisher behavior, and leader-local retry requirements.

Validation

Documentation checked against the integrated implementation. Integrated Go normal/race suites, binaries, scoped lint/actionlint, 21 frontend tests, TypeScript, and Vite build passed at this boundary. Retention benchmark: 1 vs 10,000 peers retained 9 allocations per summary serialization; wire sizes 313 vs 321 bytes. This is fixture evidence, not live-cluster or whole-process RSS measurement. Immediate-parent diff: 182 added+deleted lines.

Part of the draft lightweight-status stack based on #745.

Lightweight status draft stack

Base: #745. Each layer targets the preceding branch and remains draft.

#746 -> #747 -> #748 -> #750 -> #751 -> #752 -> #753 -> #754 -> #755 -> #756 -> #757 -> #758 -> #759 -> #760 -> #761 -> #762 -> #763 -> #764 -> #765 -> #766 -> #767 -> #768 -> #769 -> #770 -> #771 -> #772 -> #773 -> #774 -> #775 -> #776 -> #777 -> #778 -> #779 -> #780 -> #781 -> #782 -> #783 -> #784 -> #785 -> #786 -> #787 -> #788 -> #789 -> #790 -> #791 -> #792 -> #793 -> #794 -> #795 -> #796 -> #797 -> #798 -> #799

…tions

Document Load data/Refresh and CLI behavior, async detail API, TTL and transport failures, leader-local lifecycle, memory ownership, and summary-only background and bulk data.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d2243398-6c36-4c3d-969e-7ed7bfb5b459
This was referenced Sep 16, 2026
This was referenced Sep 16, 2026
@phealy

Copy link
Copy Markdown
Contributor Author

This PR was mistaken churn from splitting the lightweight-status work into unnecessarily small PRs. That was my mistake, not a requirement from the user.

Its changes are preserved in #748 within the user-approved, consolidated 12-PR draft stack. Closing this superseded PR; the implementation is not being discarded, and nothing has been merged into main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant