Orphan walk

The worker is protected by a service-token Access policy. Paste your CF-Access-Client-Id and CF-Access-Client-Secret below. They're stored in this browser's localStorage and never sent anywhere except as headers on worker requests.

Walks Comms's and Experience's Tier 1 static extractions, attempts to resolve each parentEntityKey in producedArtifacts against the current Orchestrator plan records. Surfaces three numbers per consumer: resolvable (parent exists), orphan (parent doesn't exist), unresolvable (placeholder slots in parent key — expected pre-lineage-epic). Results written to m5_ops_tier2_orphan_walk_<isoTimestamp>.

Some Tier 1 extractions are not in KV. Most agents in this build received their extractions as JSON files in chat; not all of them wrote back to KV. Upload the JSON files here as a fallback. Ops can walk against uploaded data and optionally persist it to the canonical KV keys for future use.