fix(review): pending-CI not safe-to-merge + type labels + visual after-shot self-poll

[JSONbored]

Bundles the remaining review-pipeline fixes (all deployed: pending-CI 14f83cfe).

• Pending CI is never 'safe to merge' — deriveUnifiedStatus downgrades any non-passed CI (failed→Blocked, pending/unverified→Held).
• Type labels (reviewbot auto-label parity) — new pr-type-label.ts derives one gittensor:bug/feature/priority per PR by title + changed paths, applied review-time + best-effort.
• Visual after-shot self-poll — capture.previewPending now schedules a bounded recapture-preview job (90s ×5) so the AFTER cell refills once the preview deploy is live, instead of a stuck spinner.
• Separately (live D1): AI review mode set to block (full dual review).

3460 tests pass; typecheck clean.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[ghost]

Caution

🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥

🛑 Gittensory review — blocked

8 files · 2 AI reviewers · no blockers · readiness 93/100 · CI failing · unstable

🛑 Blocked

Review summary
The pull request introduces several changes, including a new type label system, a visual after-shot self-poll feature, and modifications to the unified comment renderer. The changes appear to be well-structured and follow good coding practices. However, without a thorough review of the entire codebase, it is difficult to assess the overall impact of these changes.

Suggestions

• Consider adding a comment to `removePullRequestLabel` explaining why it ignores 404 errors.
• Consider adding a comment to `deriveUnifiedStatus` explaining the logic for downgrading CI states.
• Consider adding a comment to `resolvePrTypeLabel` explaining the priority order of label resolution.

CI checks failing

• codecov/patch — 71.42% of diff hit (target 94.93%)
• codecov/project — 94.89% (-0.05%) compared to 1f432e7

Signal	Result	Evidence
Code review	✅ No blockers	2 reviewers, synthesized
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Review load	✅ 20/20	Readiness component derived from cached public PR metadata and labels; size label size:L.
Validation evidence	✅ 25/25	PR body includes validation/test evidence.
Open PR queue	✅ 10/10	0 open PR(s), 0 likely reviewable.
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 85 PR(s), 251 issue(s).
Gate result	✅ Passing	No configured blocker found.

Nits — 1 non-blocking

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, JavaScript, Ruby, Go, Kotlin, MDX, Shell
• Official Gittensor activity: 85 PR(s), 251 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

Review details

Generated from public PR metadata and the diff. Advisory only; deterministic signals remain authoritative.

The pull request introduces several changes, including a new type label system, a visual after-shot self-poll feature, and modifications to the unified comment renderer. The changes appear to be well-structured and follow good coding practices. However, without a thorough review of the entire codebase, it is difficult to assess the overall impact of these changes.

Suggestions

• Consider adding a comment to `removePullRequestLabel` explaining why it ignores 404 errors.
• Consider adding a comment to `deriveUnifiedStatus` explaining the logic for downgrading CI states.
• Consider adding a comment to `resolvePrTypeLabel` explaining the priority order of label resolution.

• Re-run Gittensory review

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[ghost]

Gittensory approves — the gate is satisfied and CI is green.

[codecov]

Codecov Report

❌ Patch coverage is 71.42857% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 94.89%. Comparing base (1f432e7) to head (863ad12).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/queue/processors.ts	50.00%	7 Missing and 2 partials ⚠️
src/github/labels.ts	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1077      +/-   ##
==========================================
- Coverage   94.93%   94.89%   -0.05%     
==========================================
  Files         150      151       +1     
  Lines       18216    18249      +33     
  Branches     6601     6610       +9     
==========================================
+ Hits        17294    17317      +23     
- Misses        413      419       +6     
- Partials      509      513       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ghost]

Gittensory requests changes — CI is not green:

• CI is failing (codecov/patch, codecov/project)

[ghost]

Gittensory requests changes — CI is not green:

• CI is failing (codecov/patch, codecov/project)