You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
impl(collector): feed sections fail silently (omitted on error) - publish per-section status in feed meta #1178
Evidence (live review 2026-10-26 ~22:40 CDT, laptop loopback + gh, cross-checked): The collector has already shipped a feed missing whole sections without any in-band signal (Oct 26: the collector unit's env lacked the egress proxy, so unit-produced feeds silently omitted sections - PR #992 fixed that instance). The feed format still has no per-section status: a section is either there or not, and every consumer guesses why (the aggregator's "absent" misdiagnosis in the footer issue is a direct consequence).
Proposal
Feed gains meta.sections: { name: { status: ok|error|skipped, at, error? } } written by the collector for every section it attempts; aggregator provenance surfaces error states distinctly (and the health page consumes them). Backward compatible: old feeds without meta render as today.
The collector writes meta.sections into every feed: { name: { status: ok|error|skipped, at, error? } } for every section it attempts.
A collector run with a deliberately broken section source produces a feed with that section marked error + reason, and the dashboard health view shows it distinctly.
Backward compatible: feeds without meta.sections render exactly as today.
Fleet monitor intake enrichment (protocol §5) — 2026-10-28T06:26Z. This issue was filed 2026-10-27 by Drew (dezren39) from the 2026-10-26 live pm-stack review and had no priority/* label and no standard ## Acceptance criteria section; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).
Still live: verified open this run; no merged PR or commit found that implements it.
Risks: Consumers other than the aggregator read the feed — the meta addition must be purely additive. Error text must not leak secrets from section sources.
Suggested approach: Add meta.sections at the collector's section-dispatch point so every section is covered uniformly, then surface error states in the aggregator provenance/health view.
Activity
developing-today commentedon Oct 27, 2026
CODE-314
dezren39 commentedon Oct 28, 2026
Intake review
Fleet monitor intake enrichment (protocol §5) — 2026-10-28T06:26Z. This issue was filed 2026-10-27 by Drew (dezren39) from the 2026-10-26 live pm-stack review and had no
priority/*label and no standard## Acceptance criteriasection; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).kind/*(kept existing),source/human,status/needs-triage,priority/normal,effort/s,app/pm-stack(existing),meta/enriched.9 remaining items
dezren39 commentedon Nov 1, 2026
Picked up queue task 4903 for implementation; revalidating current main and related work before editing.\n\n
dezren39 commentedon Nov 1, 2026
Implementation is on PR #3943; targeted tests pass. Checking CI, then I will merge if all checks and review criteria are green.\n\n
dezren39 commentedon Nov 1, 2026
PR #3943 is merge-ready: targeted tests pass, no required status checks are configured, and the one full-suite failure reproduces on clean main.\n\n
dezren39 commentedon Nov 1, 2026
Merged PR #3943 (merge commit a10865f); queue task 4903 is complete.\n\n