[kriszyp]

⊙ Problem

1. Scoped component names (such as @scope/app-a@main) collapse under the empty-string key "" during status aggregation. StatusAggregator.aggregate splits on indexOf('@') instead of lastIndexOf('@'). get_status merges unrelated scoped components under "", and get_components reports { status: 'unknown' }.
2. In zero-worker mode (threads.count: 0), setMainIsWorker(true) makes getWorkerIndex() return 0 on the main thread, so main-thread component statuses are mislabelled worker-0 instead of main.

🤔 Why a shared parser and isMainThread?

Centralizing key parsing in one helper keeps component grouping, thread-label extraction, and abnormality normalization aligned on the last @. Checking isMainThread from node:worker_threads identifies the main thread directly without changing getWorkerIndex(), which Table.ts relies on for TTL ownership.

💡 Solution

Parse @<threadLabel> suffixes through a shared parseStatusKey helper using lastIndexOf('@'). Check isMainThread in CrossThreadStatusCollector and componentStatusRequestHandler. In zero-worker mode (threads.count: 0), get_components and get_status now report main-thread status timestamps under lastChecked.main (with lastChecked.workers empty). They key main-thread abnormalities as <component>@main instead of <component>@worker-0.

🔧 Changes

• components/status/crossThread.ts: Replace stripThreadIdentity and the three separate @ splits (StatusAggregator.aggregate, aggregateComponentGroup, and abnormality recording) with parseStatusKey(statusKey).
• components/status/crossThread.ts and server/itc/serverHandlers.ts: Use isMainThread from node:worker_threads in CrossThreadStatusCollector.getLocalStatusOnly (shared by collect() and the ITC-failure fallback) and in componentStatusRequestHandler.
• unitTests/components/status/crossThread.test.js and unitTests/server/itc/serverHandlers.test.js: Add regression tests for @-scoped component aggregation and zero-worker main-thread status labelling.

✅ Verification

• Verified all three new unit tests fail against origin/main sources before the fix (36 passing, 3 failing).
• Rebuilt (npm run build) and ran npx mocha unitTests/components/status/*.test.js unitTests/server/status/*.test.js unitTests/server/itc/*.test.js (246 passing).
• Ran npm run lint and npm run typecheck.

PR QA: none — surgical status-key parsing and thread-label check covered by unit tests

---

Author: Gemini (gemini-4-argon-high)

Release target: main — status-correctness fix for the next minor; no patch backport needed
Related PRs: #3439 overlaps, #2155 independent

Origin — the dispatch brief this PR was written from

components/status/crossThread.ts: (1) StatusAggregator.aggregate strips the @ suffix with indexOf('@') while the other two sites use lastIndexOf('@'), so scoped component names (@scope/app-a@main) aggregate under '' / truncated keys; use one shared stripping helper for all three sites. (2) In zero-worker mode (threads.count: 0) main-thread component statuses are labelled worker-0, because getWorkerIndex() (0 on the main thread) is used to pick the 'main' label in crossThread.ts and server/itc/serverHandlers.ts: use an explicit main-thread check. Leave warning/loading ranking to open PR #3439.

Acceptance

Tests: @scope/app-a@main, @scope/app-a.rest@main and @scope/app-b@worker-0 aggregate to their own names with no '' key; with threads.count: 0, main-thread statuses are labelled main. Show each new test failing on origin/main sources (forced rebuild) before the fix.

_{Dispatch: task harper-status-thread-label-and-main · queued by finding-triage/wave-40 · ran by gemini/gemini-4-argon-high/low · worker kzyp-xps-1}

_{Review-Coverage: authored=claude; ran=cursor-composer,codex,gemini; adjudicated=domain; declined=cursor-grok,muse; rounds=5; full=3 @ 0661aa7}

_{Review-Attention: read ~3m (decisions: physical-thread-identity-for-main-label, test-seam-parameter) @ 0661aa7}

[gemini-code-assist]

Code Review

This pull request refactors the cross-thread status collection and aggregation logic to correctly handle scoped component names (e.g., @scope/app-a) and to ensure that the main thread is correctly identified as "main" (with an undefined worker index) even when running in zero-worker mode (setMainIsWorker is true). It introduces a helper function parseStatusKey to parse component names, thread labels, and public names, and updates the aggregation and request handler logic accordingly. Comprehensive unit tests are added to verify these behaviors. I have no feedback to provide as there are no review comments.