Skip to content

impl(collector): feed sections fail silently (omitted on error) - publish per-section status in feed meta #1178

Closed

Description

@dezren39

Finding

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.

Acceptance

Acceptance criteria

  • 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.

Activity

  1. added
    kind/featureNew feature or capability request
    task/small-fixQueue packet kind: bounded fix with reproduction and targeted tests
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/normalOrdinary priority (the default)
    effort/sSmall: expected under 2 hours of work
    on Oct 28, 2026
  4. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    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 criteria section; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  6. 9 remaining items

  7. added
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 1, 2026
  8. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Picked up queue task 4903 for implementation; revalidating current main and related work before editing.\n\n

  9. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Implementation is on PR #3943; targeted tests pass. Checking CI, then I will merge if all checks and review criteria are green.\n\n

  10. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    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

  11. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Merged PR #3943 (merge commit a10865f); queue task 4903 is complete.\n\n

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

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/humanFiled directly by a humantask/small-fixQueue packet kind: bounded fix with reproduction and targeted tests

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions