{
  "format": "bbport-ap-native-callback-evidence-v1",
  "checked_at": "2026-10-16",
  "runtime": {
    "fork": "Supermedo/bloodborne_pc",
    "version": "windows-v1.8.2",
    "upstream": "https://github.com/Supermedo/bloodborne_pc/releases/tag/windows-v1.8.2",
    "archive_sha256": "5b97ab5abbd81bd5db80ac58f1f9c4dc5a20643563bb770b284b3da81f574031",
    "engine_sha256": "9af1fbbf9cf52ad6492f4d166558f9f0fa40d5dc712bf0fbd38695cc7ea53618",
    "platform": "Windows x64",
    "title_id": "CUSA03173",
    "app_version": "01.09",
    "save_title_id": "CUSA00207"
  },
  "tested_client": {
    "revision": "06bea76ac8f58fe967fa2823bcb08609d3198212",
    "sha256": "a7070a8365ce99af17c0877d6067a1fc156d4ea7c9fddc2b6575bd34d8e14e71",
    "runtime_build": "bb-0.1.0-r10"
  },
  "method": [
    "Stock original x86 game entry and Vulkan runtime with user-owned merged game files and disposable copied saves.",
    "Production launcher preparation/launch, native event/suppression/toast writers, native client and real private AP MultiServer.",
    "Real Generate.py seed 61337672840406993903, dedicated BBPortProof test slot; 656 locations, 340 item bindings and 59 generated native awards.",
    "Controller input through the stock runtime pad-file interface; read-only diagnostics distinguish native effects from client acknowledgments.",
    "No probe-forced event flags, injected game callbacks, assumed save binding, player game interruption or foreground input takeover. Normal production client/game flag updates remain active."
  ],
  "observations": [
    {
      "check": "save binding",
      "result": "passed",
      "detail": "The effective SFO selected CUSA00207 saves for the CUSA03173 game and bound the actual loaded character automatically."
    },
    {
      "check": "native heartbeat and consume callers",
      "result": "passed",
      "detail": "In the initial passthrough-binder canary the real game consumed a Pebble delivery: held quantity 12 to 13, native_result 13, execution_evidence true, AP index 0 acknowledged. That earlier client binary had SHA256 c73fba8e812d3d29288f2b0d26cbcde9d4873c90cbf7707c3f3e32c701e6c592."
    },
    {
      "check": "generated common-event callers",
      "result": "passed",
      "detail": "The actual generated seed processed bridge tokens 9800 and 9801 into Communion (+1 vial) rune and Old Yharnam gem instances, with acknowledgment flags 12400990 and 12400991. This initial event run used the debug build of revision 06bea76, SHA256 bcb2931b86fd73bceae37a1ce1d3625b0830d233ecb8a97a1a58924fb0a079ba; restart and equipment checks used the recorded release build."
    },
    {
      "check": "save and restart recovery",
      "result": "passed",
      "detail": "The exact release client above resumed the copied save and ledger. Both rune/gem instances remained present exactly once; pending index 1 was acknowledged without replaying ap_0 or ap_1."
    },
    {
      "check": "equipment delivery",
      "result": "passed",
      "detail": "AP index 4 inserted Reiterpallasch +2 (normalized item 10100200) through the native path."
    },
    {
      "check": "existing check reporting",
      "result": "baseline-only",
      "detail": "42 already-set Central Yharnam flags reached MultiServer. These are existing save state, not evidence of a newly collected location."
    },
    {
      "check": "duplicate unique tools",
      "result": "parked",
      "detail": "Already-owned workshop tools at AP indices 2 and 3 stayed at native quantity 1. Existing terminal-failure handling parked them while later equipment delivery advanced; these are not claimed as new grants."
    }
  ],
  "boundaries": [
    "This evidence records actual delivery/common-event callbacks and restart recovery in the named runtime. It does not claim a complete campaign, fresh pickup/boss callers, CUSA00900 live behavior, canonical Linux game execution, or another Windows fork.",
    "The recorded generated-seed restart harness encountered a transient Windows ledger read sharing error after collecting the observations. Its read retry was repaired; this was not a client or game crash. The raw run is not represented as an all-green end-to-end campaign.",
    "Additional capacity/storage-overflow delivery attempts returned native EMPTY_SLOT and parked. These attempts are not accepted deliveries. Full storage is an unverified explanation because the client cannot inspect storage contents.",
    "The native candidate adds three platform cfg declarations and documentation after the tested revision; paired package identities are verified separately.",
    "No BBPort AP player package was publicly released at this checkpoint."
  ]
}