Skip to content

pm-stack(aggregator): typecheck red on main — src/item-history.ts uses GhKind without importing it from model.ts #5247

Open

Description

@dezren39

Problem

bunx tsc --noEmit in pm-stack/aggregator fails on current main (verified at 6a1a351, clean worktree) with a second error alongside the one tracked in #5043:

src/item-history.ts(58,10): error TS2304: Cannot find name 'GhKind'.

GhKind is defined at pm-stack/aggregator/src/model.ts:24 (export type GhKind = "issue" | "pr") and used at src/item-history.ts:58 (kind?: GhKind;) without an import. Recent item-history commits (53635b5 for #5172, 8ea49db / a06bc4a for #3981) touched this file.

Evidence

Acceptance

Filed by the repo queue worker (lane code-m, task 8672) per the file-the-issue rule; the fix itself is out of scope for task 8672 / #5043, whose packet covers only the overview.test.ts fixture.

Acceptance criteria

Activity

  1. added
    kind/ciCI/CD pipelines, workflows, and build automation
    priority/highImportant and time-sensitive
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Nov 4, 2026
  2. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    main-ci watch — new main failure for this workflow (fresh round, post-fix head)

    Reusing this open issue #5247, which already tracks this exact failure: the run's Typecheck step (bunx tsc --noEmit) fails with only src/item-history.ts(58,10): error TS2304: Cannot find name 'GhKind' — verified in the run's failed log; the TS2741 conflicts error from the previous track is gone. No duplicate issue filed, per the trigger dedupe rule.

    Fresh round note: the previous main-ci track for this workflow, issue #5043, was verified CLOSED at 2026-11-04T02:29:21Z (fix PR #5248 merged as 33bdcb5), and run 41761070921 was created 2026-11-04T02:29:23Z on that post-fix head — so this is a fresh round, tracked here on #5247 instead of a new duplicate. The run completed late (updated 2026-11-04T03:47:10Z) and was caught by the failure-filtered list. This issue had no queue task (the worker that filed it noted the fix was out of scope for task 8672), so the trigger enqueues a fix task for it now.

    Filed by main-ci-failure-fix-trigger (fleet). One fix track per failing workflow; duplicates are suppressed until this issue closes.

    🤖 Agent note · filed

  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/small-fixQueue packet kind: bounded fix with reproduction and targeted tests
    source/ci-watchFiled by the main-ci-failure-fix-trigger (fleet CI watch)
    effort/xsTrivial: expected under 30 minutes of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 4, 2026
  4. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    Intake review

    🤖 Fleet monitor intake pass, 2026-11-03 run.

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/xsTrivial: expected under 30 minutes of workkind/ciCI/CD pipelines, workflows, and build automationmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivequeue/queuedHas a queued task in the Supabase agent queuesource/ci-watchFiled by the main-ci-failure-fix-trigger (fleet CI watch)status/needs-triageNot yet triaged; needs a first looktask/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