Step 7 TDD only: in the current repository, write failing tests first for deterministic goal_slug identity, canonical six-field ActorScopeKey routing, one-time actor-session resolution and immutable c

[rysweet]

Task Description

Step 7 TDD only: in the current repository, write failing tests first for deterministic goal_slug identity, canonical six-field ActorScopeKey routing, one-time actor-session resolution and immutable correlation propagation, compatible legacy reuse, incompatible isolation, scoped collision/corruption, malformed scope inputs, terminal correlation, concurrency, telemetry allowlisting, and direct incompatible rebinding. Preserve staged work. Do not implement production behavior beyond test scaffolding. Output concrete test files changed and initial expected-failure validation results.

Requirements

✓ Set NODE_OPTIONS=--max-old-space-size=32768
Requirements are clear after these binding decisions:

• Use the existing six ActorScopeKey fields verbatim; introduce no substitute identity type.
• Compatible legacy records reuse the session only when all available canonical scope and correlation data agree. Missing newly introduced metadata is tolerated; contradictory or malformed data is not.
• Resolver-level incompatibility creates isolated state. Direct rebinding of an existing session is explicitly rejected and leaves the original binding unchanged.
• Scoped collisions and persisted corruption produce explicit errors without reuse, overwrite, or cross-scope leakage.
• Repeated and barrier-controlled concurrent access resolves exactly once and returns the same immutable correlation identity.
• Terminal lookup requires matching session, goal, and cycle correlation; mismatches return an explicit failure and no terminal data.
• Telemetry assertions use the documented allowlist as a closed set and reject every additional scope or correlation field.
• Deterministic goal_slug tests include repeated calls and normalization-equivalent long titles.
• Malformed scope tests cover absent, empty, invalid, and internally inconsistent canonical fields.
• Tests must compile, initialize fixtures, reach behavioral assertions, and fail only because production behavior is missing.
• Changes are limited to test files and strictly test-only scaffolding. No production behavior, canonical contract, staged file, or unrelated work may change.
• The completion report must name every changed test/scaffolding file and identify each targeted command’s intentional assertion failures.

Acceptance Criteria

• All explicit requirements met
• Tests passing
• Philosophy compliant
• Documentation updated

Classification

Generated via default-workflow recipe