Skip to content

net-controller: bind legacy diagnostic bases to the TTL lifecycle - #778

Closed
Patrick W. Healy (phealy) wants to merge 2 commits into
phealy/lightweight-status-node-http-detailsfrom
phealy/lightweight-status-legacy-detail-store
Closed

Patrick W. Healy (phealy) wants to merge 2 commits into
phealy/lightweight-status-node-http-detailsfrom
phealy/lightweight-status-legacy-detail-store

Conversation

@phealy

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

Copy link
Copy Markdown
Contributor

Scope

Stacked on #777. Adds UID-bound legacy snapshot associations and wire-base/identity-memo ownership to the TTL store. Continuous legacy publications reuse cache associations rather than create a request per push; they do not fulfill unrelated pending refreshes. Explicit detail replacement invalidates the old legacy delta base. Consolidates correlated error handling in CompleteFailure.

This is storage foundation only; production legacy-ingestion wiring follows before client migration and final thin-cache activation. No publishing default switch.

Validation

Controller/shared-status race tests and scoped formatting/lint including actionlint passed after integration. Existing transport failure/duplicate tests use the canonical manager implementation. Below the 1,000 additions-plus-deletions ceiling.

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

Keep wire revision and identity validation memo with expiring detail snapshots. Reuse completed associations for legacy publications without fulfilling unrelated requests or accumulating records per publication. Add correlated failure completion and explicit expiry-loop error logging.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d2243398-6c36-4c3d-969e-7ed7bfb5b459
Use the request manager CompleteFailure implementation for transport errors and preserve duplicate, expiry, identity, and previous-snapshot behavior in the existing transport tests.

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 #755 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