Tracelet Foundation Worker

Example Handoff

{
  "salientSummary": "Replaced legacy string-RPC usage for settings and repo scope with typed domain APIs, fixed setup-summary invalidation after settings saves, and made runtime-unavailable states explicit for bridge-limited routes.",
  "whatWasImplemented": "Updated shared frontend contract types, split transport adapters from page-facing APIs, repaired settings invalidation so Setup, Repo Pulse, and Hygiene refresh after scope changes, and added explicit unavailable-state handling where browser mode previously looked like empty data.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "pnpm typecheck",
        "exitCode": 0,
        "observation": "Typed domain API changes remained consistent across hooks and routes."
      },
      {
        "command": "cargo test --manifest-path src-tauri/Cargo.toml -- --test-threads=5",
        "exitCode": 0,
        "observation": "Rust tests still passed after shared contract and invalidation changes."
      },
      {
        "command": "cargo fmt --manifest-path src-tauri/Cargo.toml --check",
        "exitCode": 0,
        "observation": "Rust formatting check passed."
      }
    ],
    "interactiveChecks": [
      {
        "action": "Saved new code directories in Settings, then revisited Setup, Repo Pulse, and Hygiene without reloading.",
        "observed": "All three surfaces reflected the new scope in the same session."
      },
      {
        "action": "Opened a bridge-limited route in browser-only mode.",
        "observed": "The route showed truthful unavailable messaging instead of a misleading empty state."
      }
    ]
  },
  "tests": {
    "added": [
      {
        "file": "src/.../shared-contract-tests.*",
        "cases": [
          {
            "name": "settings invalidation refreshes setup summary and repo-backed queries",
            "verifies": "Scope changes propagate coherently across major surface families."
          }
        ]
      }
    ]
  },
  "discoveredIssues": []
}

When to Return to Orchestrator

• The shared change would silently broaden product or provider scope.
• A page relies on an undefined contract and needs a product decision before cleanup can continue.
• Runtime-validation limits make it impossible to prove a shared behavior through the allowed surfaces.