Skip to content

status-core: integrate accepted nodeprobe four-axis state - #66

Open
Florious95 wants to merge 2 commits into
mainfrom
pr/status-core-exact-nodeprobe
Open

status-core: integrate accepted nodeprobe four-axis state#66
Florious95 wants to merge 2 commits into
mainfrom
pr/status-core-exact-nodeprobe

Conversation

@Florious95

@Florious95 Florious95 commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Goal

Make accepted nodeprobe the sole Rust/Go status authority and carry independent provider, activity, nullable session_name, and health through Go wire and APP workspace data, with legacy status == activity.

Accepted source/runtime

  • Product base: 4605951e427f9ba6627375498dcb3c757c05bf36
  • Accepted source: ff316dc0afe8ab280e61d30934e7624579be6224, tree 5217a41aa914ddcb72c27f39f1b4af9ead68b1b6
  • macOS arm64 binary: size 781728, SHA-256 4ae8a87380025f810dad221f96b64764e4a312ae6de127d83cc641884d60a5d9
  • Official Pi extension: size 3406, SHA-256 fce8c7fac3b4274d3c8e38261022b6ae31ad021247b7ff39bbf0f6dd04088850
  • Canonical corpora only: tools/nodeprobe/fixtures/{titles,providers}.tsv

Changes

  • Synchronized all 14 frozen source/test/doc blobs byte-for-byte and added embedded accepted-source manifest plus static provenance gate.
  • Added typed direct Go runner, startup capability verification, once-per-socket sampling, and structural join by socket/session/window/pane only.
  • Preserves unknown-provider rows and last good snapshots on whole-socket failure; zero consumers perform zero status polling.
  • Replaced runtime Cargo launcher with manifest-aware accepted-binary launcher.

Deleted authorities

Removed ProviderFinder/procFinder, provider table/load, title/footer detector registry and provider-specific detectors/tests. No legacy fallback remains.

Four-axis APP chain

Go listing/delta/level2 emits all four axes and status == activity; Kotlin decodes additive fields, derives fail-closed effective activity (including old-server status compatibility), and carries provider/activity/name/health through toL2Entry and cache replacement. No Provider icon or session-ui work.

Tests/CI

  • Rust locked isolated target: 35 passed, 0 failed.
  • Node Pi extension: 1 passed, 0 failed.
  • Go non-cached changed packages: all passed, 0 failed.
  • APP JVM --rerun-tasks: 605 passed, 0 failed.
  • Provenance/static gate: passed; 14 synchronized blobs, exact runtime hashes, exactly two canonical TSVs, no old call edges.
  • Strict T3 base/head comparison: command remains exit 1 on the exact pre-existing repository inventory (same 18 T3-1, 1 T3-2, 34 T3-3); PR-local findings are zero and obsolete provider dependency findings decrease. This is recorded as baseline red, not green.
  • CI status must be judged on each filtered PR head; installed macOS binary authority is the subscription-machine receipt in .team/stable-pr/status-core/evidence/.

Known upstream risks

Accepted source behavior is unchanged: future timestamps within its tolerance and challenge response socket_path are recorded upstream risks. No product-side timestamp/path shadow rule was added.

Compatibility

Protocol version, refs, bridge routing, cwd grouping, names/title bytes, dimensions, terminal control, and old-client status remain compatible. Unsupported production platforms fail explicitly.

Rollback

Revert this atomic source commit/mirrored pair to restore old consumers. No accepted external rollout asset was modified. Do not merge without independent acceptance and explicit authorization.

REWORK-001 synchronization proof

  • Test-only scope: server/internal/api/level2_test.go; production level2, accepted source/corpora, Provider UI, and session UI unchanged.
  • The zero-subscriber test now waits for the mandatory post-auth listing sample before baseline capture, synchronizes subscribe/unsubscribe state, drains permitted in-flight work, and checks stable discovery plus nodeprobe counters.
  • Frozen counterexample: removing either production zero-subscriber guard makes both counters grow and fails the assertion.
  • Targeted stability (single invocation): go test -count=20 ./internal/api -run '^(TestL2NoPollWithoutSubscriber|TestLevel2StopsWhenNoSubscriber)$' — PASS, exit 0, 18s (package 15.823s).
  • Exact four packages (single invocation): go test -count=1 ./cmd/agentmirrord ./internal/nodeprobe ./internal/api ./internal/protocol — PASS, exit 0, 54s.
  • Provenance gate (single invocation): PASS, exit 0, 1s; accepted commit/tree and 14 synchronized files unchanged.
  • No command was retried to green. Strict-T3 base/head same-red evidence and PR-local=0 remain unchanged.

@Florious95 Florious95 changed the title pr/status-core-exact-nodeprobe status-core: integrate accepted nodeprobe four-axis state Sep 1, 2026
@Florious95

Copy link
Copy Markdown
Owner Author

Delivery receipt: local owning commit f1c4fdd4da64efa220d15ee4a9b1759709e6c1a5; filtered core head 5a5ae284cf468775de5c00bfa8e1937451b3eb6e; local/remote app tree both 58e6b33f981d660ad5a6f03aafd9716330891c43. PR state verified OPEN. No GitHub status checks are configured (statusCheckRollup=[]), so online CI is unjudgeable rather than inferred green. Local non-cached evidence and strict-T3 base/head baseline-red comparison are committed under .team/stable-pr/status-core/evidence/.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants