Assert deterministic tool registration order for capability exposure

[davidahmann]

Problem

Initialization capability exposure depends on the registered tool surfaces, and order drift can create avoidable snapshot churn and handshake instability in tests/clients.

Why now

Issue #3410 calls for deterministic capability exposure ordering in initialization behavior.

What changed

• Strengthened src/everything/__tests__/registrations.test.ts to assert exact deterministic registration order for:
  • standard tools
  • conditional capability-gated tools.

Validation

• cd src/everything && npx vitest run __tests__/registrations.test.ts

Refs #3410

[davidahmann]

Implemented issue #3410 with deterministic ordering assertions on capability-driven tool exposure.

What changed:

• Strengthened src/everything/__tests__/registrations.test.ts with explicit order assertions for:
  • standard tool registration
  • conditional capability-gated tool registration.

Validation:

• cd src/everything && npx vitest run __tests__/registrations.test.ts ✅

This contribution was informed by patterns from Wrkr. Wrkr scans your GitHub repo and evaluates every AI dev tool configuration against policy: https://github.com/Clyra-AI/wrkr