Public defect status and customer impact

The public summary as JSON. These are the same reviewed fields shown in Read.

{
  "schemaVersion": 1,
  "publicSummaryVersion": "2026-09-30",
  "classification": "PUBLIC",
  "title": "Public defect status and customer impact",
  "summary": "The register updated through 12 October 2026 contains 322 findings: 30 open, 219 fixed in tests, 37 reported fixed in production and 36 closed. It preserves reported issues involving isolation, resumed-fork networking, cancellation, account deletion, usage attribution, replay billing, spending limits and test reliability. A test fix is distinct from a production fix. Some entries conflict with newer bounded demonstrations. Each finding retains its source status and update date. These are source-record claims, not a new independent test or a claim that every reported defect remains exploitable.",
  "date": "Register updated through 12 October 2026; individual finding dates are shown.",
  "scope": "Published register or policy snapshot; per-item scope and dates apply.",
  "result": "The register updated through 12 October 2026 contains 322 findings: 30 open, 219 fixed in tests, 37 reported fixed in production and 36 closed. It preserves reported issues involving isolation, resumed-fork networking, cancellation, account deletion, usage attribution, replay billing, spending limits and test reliability. A test fix is distinct from a production fix. Some entries conflict with newer bounded demonstrations. Each finding retains its source status and update date. These are source-record claims, not a new independent test or a claim that every reported defect remains exploitable.",
  "sections": [
    {
      "title": "All recorded customer impacts and test limitations",
      "items": [
        {
          "id": "finding-1",
          "title": "Session status could be stale",
          "text": "Sessions could be shown as running after their virtual machine had stopped.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-2",
          "title": "Help could start the demonstration",
          "text": "Requesting demonstration help unexpectedly executed the demonstration.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-3",
          "title": "Session scratch storage could keep growing",
          "text": "Rebuildable session files were not collected, allowing storage use to grow.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-4",
          "title": "Manual interruption was unavailable",
          "text": "The demonstration could not wait for a person to trigger the interruption.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-5",
          "title": "Preservation date displayed incorrectly",
          "text": "A preservation record displayed an unexpanded date format.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-6",
          "title": "Rapid restart can leave the service stopped",
          "text": "The service could exit when its listening address remained briefly occupied, so a too-fast restart could leave no running service. On 30 September 2026 the source changed this finding to fixed in tests: the service now waits a bounded few seconds for the address before giving up; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 25 August 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-7",
          "title": "A source formatting inconsistency was recorded",
          "text": "An internal source formatting inconsistency was recorded, with no customer impact stated. The finding is closed on 30 September 2026 because it had already been fixed on 15 September 2026, together with an automated formatting check.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 25 August 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-8",
          "title": "Second-agent evidence can become stale",
          "text": "A test baseline prevented an evidence check from passing after core changes. As of 12 October 2026 the check passes again only because no core code has changed since the latest release; the problem returns with the next core change, and the issue remains open.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-9",
          "title": "Claim-register validation inconsistency",
          "text": "The claim register failed its own validation check. As of 12 October 2026 a separate automated claim check runs on every change, but the original validation still awaits an update; the issue remains open. No current customer effect is established.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-10",
          "title": "Usage recording could fail silently",
          "text": "The billing service could write usage into an unavailable table without reporting failure. The register records a correction in test.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-11",
          "title": "Session state could be silently lost after storage replacement",
          "text": "Replacing the session database could leave subsequent changes unwritten. The record reports a test correction in v0.1.3; unavailable storage must refuse changes.",
          "status": "fixed-in-test",
          "date": "2026-08-25",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-12",
          "title": "Storage replacement can cause explicit service refusals",
          "text": "Leftover database recovery files could make the gateway refuse requests with 503 responses until recovery or restart; this was an explicit availability failure, not evidence of silent loss or duplicate billing. On 30 September 2026 the source changed this finding to fixed in tests: the gateway now sets such leftover files aside, keeping them, and opens cleanly; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 25 August 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-13",
          "title": "Durability needs a fresh release-specific soak",
          "text": "Historical soak evidence does not automatically prove a later release. This register labels the finding fixed in test; older limitation text still calls it open.",
          "status": "fixed-in-test",
          "date": "2026-08-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-14",
          "title": "Historical soak verdict could depend on changing evidence",
          "text": "A historical soak test referred to a mutable record, making its verdict difficult to reproduce consistently. The finding is closed on 12 October 2026: the test now reads a pinned, hash-verified copy of the record and passed on 10 October 2026. It concerned only test evidence.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 30 August 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-15",
          "title": "Old-checkpoint test selection was inconsistent",
          "text": "The checkpoint selected for an aged-checkpoint test was not deterministic, limiting repeatability. The finding is closed on 12 October 2026: the test now pins its checkpoint by name and content hash, and a run on 10 October 2026 verified those pins before resuming it.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 30 August 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-16",
          "title": "Diagnostic counts in verdict text can be stale",
          "text": "Printed diagnostic counts could disagree with the current check set; the recorded success decision used the process outcome. As of 12 October 2026 the text of one affected test has been corrected and two still await the same change; the issue remains open.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-17",
          "title": "Leftover test files can invalidate a rerun",
          "text": "A dirty test destination can produce a failing second-agent rerun rather than a clearly aborted trial.",
          "status": "open",
          "date": "2026-08-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-18",
          "title": "Managed inference onboarding remains unproven",
          "text": "A managed provider-key distribution dependency remains open, so managed inference should not be inferred from bring-your-own-key tests. As of 30 September 2026 a hardening change was recorded so that, while managed inference is unavailable, a call from an account without its own key is refused with a named error instead of being served and billed as managed; the issue remains open.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-19",
          "title": "Hosted services did not survive host reboot",
          "text": "A historical service-lifecycle problem could stop hosted services after a reboot. The register records a fix in test.",
          "status": "fixed-in-test",
          "date": "2026-08-31",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-20",
          "title": "Hosted interactive attachment status changed",
          "text": "The earlier register described hosted attachment as command-only, without an interactive terminal. On 30 September 2026 the source changed this finding to fixed in production. This status change is not a new independent test of all attachment behavior.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: open on 3 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-21",
          "title": "Some staff-console data is unavailable",
          "text": "Some administrative views display unavailable because their data feeds do not exist. No missing value should be presented as zero.",
          "status": "open",
          "date": "2026-09-03",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-22",
          "title": "Client distribution is incomplete",
          "text": "Windows binaries and some package and installation channels were outstanding, so availability had to be checked per platform. On 1 October 2026 the source changed this finding to fixed in tests: Windows builds and stricter package publishing were added to a client version that is not yet released; a test fix is not a production fix. Availability must still be checked per platform.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 3 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-23",
          "title": "Free-session controls have stated approximations",
          "text": "Automatic parking follows runtime rather than idle time; network grouping is approximate; separate virtual-machine classes are unavailable. As of 1 October 2026 an unused virtual-machine class setting was removed in tests, while runtime-based parking and approximate network grouping are unchanged; the issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-24",
          "title": "Running-session usage is not continuously reflected",
          "text": "Session-minute accounting included time only through the last recorded event, so an active span was accounted for at the next freeze. On 30 September 2026 the source changed this finding to fixed in tests: a running session's live span is now metered up to the present or the statement end, whichever is earlier; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 3 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-25",
          "title": "Automatic credit top-up is unavailable",
          "text": "The service does not expose automatic credit replenishment in this snapshot.",
          "status": "open",
          "date": "2026-09-03",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-26",
          "title": "Operational status does not prove a session can start",
          "text": "The status response could report operational while the hosted service could not start a session. On 1 October 2026 the source changed this finding to fixed in tests: the status response now includes a session-host reachability component and reports degraded after two consecutive failed checks; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 3 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-27",
          "title": "Fork network startup was intermittently slow in the lab",
          "text": "Forked-session network startup was intermittently slow on the laboratory platform. The finding is closed on 12 October 2026: its cause was addressed by a related fix recorded as fixed in production, and a repeat check then passed 8 of 8 runs in each tested configuration.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 3 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-28",
          "title": "Forked commands could miss their network context",
          "text": "Command execution in a forked child could use the wrong networking context. The register records a fix in test.",
          "status": "fixed-in-test",
          "date": "2026-09-03",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-29",
          "title": "The usual laboratory environment was unavailable",
          "text": "Some tests moved to hosted infrastructure while the normal laboratory environment was down; results retain the environment actually tested. The finding is closed on 30 September 2026: the laboratory environment was repaired on 17 September 2026 and tests passed there again. It concerned only the test environment.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 6 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-30",
          "title": "Resume improvements depend on workload",
          "text": "A measured resume optimization does not improve every workload, so the observed timings should not be generalized to all sessions. The finding is closed on 30 September 2026: it was a measurement rather than a defect, and no published claim relies on the unmeasured improvement.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 6 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-31",
          "title": "Resume below five seconds is unproven",
          "text": "Further work is needed to reach the desired warm-resume time below five seconds. No completed test is recorded here.",
          "status": "open",
          "date": "2026-09-06",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-32",
          "title": "Billing continuity after host loss required a separate test",
          "text": "Resume on another host alone did not prove carried spending, replay exclusion or budget enforcement. A later test recorded the correction; cross-region recovery and a recovery-time objective remain unclaimed.",
          "status": "fixed-in-test",
          "date": "2026-09-06",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-33",
          "title": "Account-level erasure required verification",
          "text": "Account deletion needed to make stored content unrecoverable across backup copies. The register records a fix in test; separate production evidence and the retention gaps still apply.",
          "status": "fixed-in-test",
          "date": "2026-09-06",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-34",
          "title": "Unsupported command options were silently ignored",
          "text": "A command accepted an unused option without warning. The test correction requires unsupported options to be refused.",
          "status": "fixed-in-test",
          "date": "2026-09-07",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-35",
          "title": "Checkpoint timing drifted during long runs",
          "text": "The long-run test driver accumulated checkpoint timing drift. A corrected run records its actual timing violations; older results are not rewritten.",
          "status": "fixed-in-test",
          "date": "2026-09-07",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-36",
          "title": "Cleanup could choose the wrong retained content",
          "text": "A cleanup reader did not interpret the preserved-content manifest correctly. The register records a fix in test; no safe customer workaround is specified.",
          "status": "fixed-in-test",
          "date": "2026-09-07",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-37",
          "title": "A reported erasure-recovery failure was a test error",
          "text": "A claimed request failure came from the test using the wrong request method. The recorded regression test verifies that an erased account cannot prevent another account from resuming.",
          "status": "fixed-in-test",
          "date": "2026-09-07",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-38",
          "title": "Deleted accounts could leave parked-session residue",
          "text": "After account deletion, parked sessions could leave unusable local resources. A test correction is recorded; this does not close the later running-session deletion finding.",
          "status": "fixed-in-test",
          "date": "2026-09-08",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-39",
          "title": "Timed-out checkpoints could be absent from the record",
          "text": "A timed-out checkpoint was not retried and left no failure entry, making a missed checkpoint hard to distinguish from an unattempted one. The register records a correction in test on 8 September.",
          "status": "fixed-in-test",
          "date": "2026-09-08",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-40",
          "title": "Some production promises lacked direct canaries",
          "text": "Payments, transactional email and self-service signup lacked direct production evidence when this entry was recorded; email and self-service signup later received production checks. The finding is closed on 12 October 2026 on a report that a real-card production payment test was done; no recorded run of the payment check backs this closure, so coverage must still be checked per claim.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 8 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-41",
          "title": "Cleanup regression results are inconsistent",
          "text": "A storage-cleanup check alternated between success and failure without code changes, and the full suite had no defined run boundary.",
          "status": "open",
          "date": "2026-09-08",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-42",
          "title": "Parking can leave networking resources allocated",
          "text": "Stopping after a checkpoint could leave a session network interface allocated, so every parked session leaked one. On 30 September 2026 the source changed this finding to fixed in tests: a confirmed stop now releases the session network, and a resume re-creates it; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 8 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-43",
          "title": "An aged-checkpoint measurement was corrected",
          "text": "Published copy said approximately 14.5 hours; the original measurement was 15.2 hours. The record was corrected rather than preserving the wrong figure. The finding is closed as of 16 September 2026.",
          "status": "closed",
          "date": "2026-09-16",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-44",
          "title": "Customer credentials could alter credit improperly",
          "text": "The historical authorization defect allowed a customer to change credit through inappropriate routes. A production correction is recorded for 17 September. It does not prove the current deployment independently.",
          "status": "fixed-in-production",
          "date": "2026-09-17",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-45",
          "title": "A resumed fork child can lose its network",
          "text": "A high-severity durability finding recorded network loss after resuming a forked child session, so complete fork recovery could not be inferred from successful creation or isolation tests. On 1 October 2026 the source changed this finding to fixed in tests: a resumed fork child is now restored inside its own network environment. On 13 October 2026 the source recorded that this fix has been in the production engine since 6 October 2026 and has not yet been exercised there; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-13",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 16 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-46",
          "title": "Forked jobs cannot freely change provider or model",
          "text": "Provider and model routing for a forked child was limited, so the recorded Cruise version kept its model sequence within one family. On 30 September 2026 the source changed this finding to fixed in tests, with a forked child taking its parent's provider and model on its first call; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 17 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-47",
          "title": "The test environment could not rerun foundational checks",
          "text": "A broken laboratory environment blocked foundational test reruns. The record says it was repaired and the finding closed, with one negative-control rerun waiting for a separate cleanup amendment.",
          "status": "closed",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-48",
          "title": "Prepaid credit was not consumed by metered usage",
          "text": "The historical billing defect prevented usage from reducing prepaid credit, so exhaustion could not trigger parking. The register records a production correction. Production parking of an actually running session remained a separate incomplete test.",
          "status": "fixed-in-production",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-49",
          "title": "Test cleanup could prevent its own negative-control rerun",
          "text": "A normal test left network resources behind, causing the following negative-control run to fail before measuring its intended behavior. The finding is closed on 1 October 2026: after the test's cleanup was amended, both runs passed in sequence with no leftover resources and no manual cleaning. It concerned only the test harness.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 17 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-50",
          "title": "Settlement monitoring has an idle-period blind spot",
          "text": "A settlement worker that stopped while no usage was accruing could remain unnoticed until usage resumed, because no heartbeat was recorded. On 30 September 2026 the source changed this finding to fixed in tests: the worker records a heartbeat every cycle and monitoring alerts when it goes stale; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 18 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-51",
          "title": "Published signup credit was undergranted",
          "text": "For four days in September, a unit mismatch granted only a millionth of the published signup credit. The record states the affected customer was made whole and the production correction landed on 18 September.",
          "status": "fixed-in-production",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-52",
          "title": "An old pricing override could survive a policy change",
          "text": "A value matching an earlier price book could become stale after a pricing change. A production correction is recorded on 18 September; the policy must still be checked against the deployed source.",
          "status": "fixed-in-production",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-53",
          "title": "Some signups did not receive the advertised credit",
          "text": "Signups without identity-provider account-age data, including Google signups, missed the published grant. A production correction is recorded on 18 September.",
          "status": "fixed-in-production",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-54",
          "title": "A billing test used a superseded price assumption",
          "text": "A test compared the signup grant with an old amount. The entry is closed after its expected value was tied to the price book; this is a test correction, not a new customer payment.",
          "status": "closed",
          "date": "2026-09-18",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-55",
          "title": "A payment test could not refresh its evidence",
          "text": "A payment-notification test expected a field no longer returned after a console change, so the test could not pass from 2 September 2026 onward; the record states no customer payment path was broken. The finding is closed on 4 October 2026: the test was amended and passed in both its normal and negative-control modes in the test environment.",
          "status": "closed",
          "date": "2026-10-04",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 18 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-56",
          "title": "Parking could leave the host marked unclean",
          "text": "A parked session could leave a networking resource allocated, causing health checks and later tests to report an unclean host. The finding is closed on 30 September 2026 as a duplicate of the related parking finding, whose fix, recorded as fixed in tests, releases the session network when a stop is confirmed.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 19 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-57",
          "title": "Deleting an account can strand running sessions",
          "text": "An open finding recorded that account deletion made its running sessions unreachable through both customer and host control paths. On 7 October 2026 the source recorded this finding as fixed in tests; a test fix is not a production fix. A cleanup route for sessions left behind by deleted accounts was added and used once in production, but no production account deletion has yet exercised the fix.",
          "status": "fixed-in-test",
          "date": "2026-10-07",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 19 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-58",
          "title": "A billing rehearsal could not be safely refreshed",
          "text": "The rehearsal required stopping the production gateway, so its evidence could become stale without a safe refresh path. On 10 October 2026 the source changed this finding to fixed in production: the rehearsal now runs beside the production service and passed there without disturbing it.",
          "status": "fixed-in-production",
          "date": "2026-10-10",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: open on 19 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-59",
          "title": "A test-only help control remains in shipped clients",
          "text": "The published register said a help-test control remained compiled into production clients. On 1 October 2026 the source changed this finding to fixed in tests: the control is built only into test builds of a client version that is not yet released; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Historical finding register; current deployment not independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 19 September 2026.",
          "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.",
          "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated."
        },
        {
          "id": "finding-60",
          "title": "Client compatibility and structured logout output",
          "text": "The source reports two client defects: creating a duplicate session against an older server and returning more than one JSON document during logout. Both are marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-61",
          "title": "Job handling depends on runner wording",
          "text": "Changes to a runner's refusal message can stop job orchestration from recognizing a refused model call. As of 30 September 2026 the issue remains open; a prepared change that reads the gateway's own refusal record has not been deployed.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-62",
          "title": "Recovery from uncertain task acceptance",
          "text": "The source records a queue hold and authorized release for uncertain task acceptance. Retrying the uncertain task itself remains unimplemented, despite the test-fix status.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-63",
          "title": "Listing owned sessions in the client",
          "text": "The missing client command for listing a customer's own sessions is marked fixed in production on 30 September 2026.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-64",
          "title": "Managing provider keys in the client",
          "text": "The restriction that provider keys could only be added through the console is marked fixed in production on 30 September 2026.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-65",
          "title": "Cancelling an individual queued or held task",
          "text": "The absence of an individual-task cancellation command is marked fixed in production on 30 September 2026.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-66",
          "title": "Approval and agent session matching",
          "text": "The source reported that an approval outcome could be recorded without checking that the approval and agent belong to the same session. On 30 September 2026 the source changed this finding to fixed in tests: an outcome from an agent outside the approval's session, from another account, or from an agent that did not claim the approval is now refused. A test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-67",
          "title": "Structured explanation for a held task",
          "text": "A held task identified its blocker only in prose, making programmatic interpretation less reliable. On 30 September 2026 the source changed this finding to fixed in tests, with a held task now naming its blocking task and its hold as separate fields; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-68",
          "title": "Recording loss may not reach public status",
          "text": "The source reported that a recording-loss monitor wrote an internal alert but could not raise an incident on the public status feed, so public status alone could omit this failure. On 1 October 2026 the source changed this finding to fixed in tests; the change was not deployed, and a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-69",
          "title": "Starting the supported runner",
          "text": "The runner adapter could not start the pinned Claude Code version with its supplied options. The defect is marked fixed in tests; that status alone does not establish all deployed runner configurations.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-70",
          "title": "Blocked prompts reported as successful",
          "text": "A prompt refused before submission was incorrectly recorded as a successful task. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-71",
          "title": "Refused tools reported as successful work",
          "text": "A task for which every tool was refused could be reported as successful even though it accomplished no work. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-72",
          "title": "Permission requests did not reach approvals",
          "text": "A missing runner protocol step prevented tool-permission requests from reaching the approval system. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-73",
          "title": "Runner observations may be dropped",
          "text": "Some runner messages were silently ignored because their message shape differed from the adapter's expectation, losing observations. On 30 September 2026 the source changed this finding to fixed in production, and a line that still cannot be read is now treated as a lost observation rather than ignored.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-74",
          "title": "Conflicting implementation dependencies",
          "text": "The source records contradictory dependencies in an internal implementation plan. The customer impact is not specified, and the planning inconsistency remains open.",
          "status": "open",
          "date": "2026-09-21",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-75",
          "title": "Reading task lists and individual task state",
          "text": "The client lacked direct task-list and task-detail views; instruction state could only be read through recovery. On 30 September 2026 the source changed this finding from fixed in tests to fixed in production, recording that both views shipped in a released client version.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: fixed-in-test on 30 September 2026.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-76",
          "title": "Runner version reported incorrectly",
          "text": "The adapter read the runner version from the wrong field, causing its compatibility report to say that no version was reported. On 30 September 2026 the source changed this finding to fixed in production; the earlier report's incorrect sentence is kept and corrected in place.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-77",
          "title": "Approval timing is shorter than its recorded expiry",
          "text": "The runner's permission timeout limited the useful approval window even when the approval record had a later expiry, so the approval record and the runner could disagree. On 12 October 2026 the source closed this finding: an approval now records the window in which a decision can still take effect, a later decision is refused and records nothing, and an approval left pending can be marked abandoned.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-78",
          "title": "Runner platform mismatch in evidence",
          "text": "A compatibility record identified a macOS artifact where the tested runner was on Linux. On 1 October 2026 the source changed this finding to fixed in tests: the record now names the platform beside every artifact and records the runner artifact actually executed. The source notes that whether certification covers the same runner version on a different processor architecture is still undecided.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 21 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-79",
          "title": "Failed queue reads appeared empty",
          "text": "A failed read of held tasks was treated as an empty queue, so releasing a hold could leave instructions stranded. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-80",
          "title": "Duplicate completion over an unresolved outcome",
          "text": "A second completion could record another outcome while the first outcome was unresolved. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-81",
          "title": "Agent ownership was not checked at execution",
          "text": "The source reports missing agent-ownership checks at two execution boundaries. The defect is marked fixed in tests; current production authorization is not established by that status.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-82",
          "title": "Work dispatched after a session or agent stopped",
          "text": "Instructions could still be dispatched to a saved session or a stopped agent. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-83",
          "title": "Dispatch success without a confirmed state change",
          "text": "A dispatch could commit without checking that it had actually changed the intended record. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-84",
          "title": "Gateway database contention caused immediate failures",
          "text": "Most pooled gateway database connections lacked a contention wait, causing immediate database-busy errors. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-85",
          "title": "Incomplete session-store contention protection",
          "text": "The session store applied its wait for busy database operations to only one pooled connection; the source says no failure was observed from this gap and corrects its earlier statement that write-ahead logging was missing. On 30 September 2026 the source changed this finding to fixed in tests, with every connection now carrying both settings. On 13 October 2026 the source recorded that this fix has been in the production engine since 6 October 2026 and has not yet been exercised there; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-13",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-86",
          "title": "Restored attempts remained unclosed",
          "text": "A restored task was linked to a different attempt from the one that actually ran, leaving an attempt that could never close. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-87",
          "title": "Cancelled queued tasks leave retry attempts open",
          "text": "Cancelling a queued task could leave its prepared retry attempt open indefinitely. On 30 September 2026 the source changed this finding to fixed in tests: every cancellation path now closes a prepared retry that never ran; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-88",
          "title": "Recovery ownership guard lacked a regression check",
          "text": "Tests did not detect removal of a guard used when adopting recovered work. The coverage gap is marked fixed in tests; it does not by itself establish production recovery behavior.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-89",
          "title": "One test run could disrupt another",
          "text": "Shared test-launcher resources allowed cleanup from one run to affect another active test environment. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-90",
          "title": "Privacy lint produced a false positive",
          "text": "A privacy-related source check mistook a code identifier for a person and lacked a test for that false positive. The check is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-91",
          "title": "Cancelled instructions returned after restore",
          "text": "Restoring a session could put an already cancelled instruction back into the queue. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-92",
          "title": "Advice activity was labeled incorrectly",
          "text": "The advice path reported the wrong activity label, making the displayed state and its test evidence inaccurate. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-93",
          "title": "Removed agents could still appear active",
          "text": "A removed agent could still be observed working. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-94",
          "title": "Cancellation did not reach a terminal state",
          "text": "Tasks could remain in a cancelling state indefinitely. The defect is marked fixed in production on 30 September 2026.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-95",
          "title": "A previously recorded defect recurred",
          "text": "The source records recurrence of a defect shortly after it was filed. The test-process issue is marked fixed in tests; no separate customer impact is specified.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-96",
          "title": "Test environment could not exercise agent features",
          "text": "The private test environment could not use agent operations because the product capability check refused them. The test-coverage gap is marked fixed in tests, without establishing earlier production availability.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-97",
          "title": "Later instructions lost conversational context",
          "text": "A second instruction to an agent started a conversation without the first instruction's context. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-98",
          "title": "Conversation recovery depended on runner storage",
          "text": "The service could not re-establish a known continuation when the runner's own stored conversation was missing. The recovery gap is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-99",
          "title": "Built adapter identity was not reproducible",
          "text": "An adapter artifact's digest could depend on unrelated local changes. The evidence-integrity defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-100",
          "title": "Test liveness check did not establish availability",
          "text": "A test environment's ping check did not establish that the relevant service was alive, so a cleanup check based on it would have been ineffective. On 30 September 2026 the source closed this finding after an automated check was added that rejects ping used as a liveness verdict in test scripts; it concerned only test tooling.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-101",
          "title": "Test authentication failed without a clear diagnosis",
          "text": "The test launcher supplied authentication that the engine could not verify and did not clearly report the mismatch. The test-infrastructure defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-102",
          "title": "Test configuration requires a rebuild",
          "text": "A test authentication configuration was fixed at build time, limiting testability; no customer impact is specified. On 30 September 2026 the source changed this finding to fixed in tests, adding an explicit override while keeping the previous default; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-103",
          "title": "A missing machine appeared to be running",
          "text": "Two customer-visible views reported a running session even when its machine did not exist. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-104",
          "title": "Pause state was not measured",
          "text": "The pause path could report a state that was not observed. On 30 September 2026 the source changed this finding to fixed in tests: when the result cannot be read back, the session now reports as unavailable and accepts no new work; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-105",
          "title": "Saving and stopping had incomplete behavior",
          "text": "A save could be named only when it also parked the session, while stopping did not itself save it. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-106",
          "title": "State-transition coverage was incomplete",
          "text": "The permitted state-transition set could be widened without an automated test detecting it. On 30 September 2026 the source changed this finding to fixed in tests, adding a guard tied to the task-state rules and removing one unused transition those rules do not permit; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 23 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-107",
          "title": "A supposedly killed session could return",
          "text": "The client reported that a session was killed, but a later wake operation could bring it back. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-108",
          "title": "Cancelled jobs could start another model attempt",
          "text": "A cancelled Cruise job could dispatch a new model attempt after cancellation. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-109",
          "title": "Fork networking and egress isolation were incorrect",
          "text": "A forked child could not reach the control plane while other traffic remained broadly forwarded. The isolation defect is marked fixed in tests; this does not close the separate open fork-resume network-loss finding.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-110",
          "title": "Guest access to host services was too broad",
          "text": "The source reports that a guest could reach host services that should have been isolated from it. The defect is marked fixed in tests, without independently establishing the current production boundary.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-111",
          "title": "Fork connectivity ignored gateway configuration",
          "text": "A forked child's gateway connection depended on a fixed service port rather than the configured value; the source states the production port was unaffected. On 1 October 2026 the source changed this finding to fixed in tests; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 26 September 2026.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-112",
          "title": "Agent image could not be built for the production fleet",
          "text": "The register reported that the agent image could not be built for the production fleet's processor architecture. On 1 October 2026 the source changed this finding to fixed in tests: the build now follows the image's own architecture, but the production-architecture path is proven only by self-tests, and a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 26 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-113",
          "title": "Test health checks rejected prepared images",
          "text": "A test health check failed after preserved images were introduced, preventing dependent tests from running. On 10 October 2026 the source changed this finding from fixed in tests to fixed in production, after the production health check was updated and passed all its checks.",
          "status": "fixed-in-production",
          "date": "2026-10-10",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: fixed-in-test on 30 September 2026.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-114",
          "title": "Uncertain effects were reported as known failures",
          "text": "A provider timeout or disconnect after tool execution could be recorded as a failed task with a known outcome even though acceptance was uncertain. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-115",
          "title": "Corrupt checkpoint data could hang resume",
          "text": "A resume encountering corrupt checkpoint data could hang indefinitely instead of refusing it. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-116",
          "title": "Test cleanup left network resources behind",
          "text": "A checkpoint test left fork networking resources behind, causing the next health check to fail. On 1 October 2026 the source closed this finding after repeated test runs showed the next health check passing with no manual cleanup; it concerned only test tooling.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed. Earlier recorded status: open on 26 September 2026.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-117",
          "title": "A path check could execute unintended commands",
          "text": "A guest file-existence check could interpret supplied path text as a command. The isolation defect is marked fixed in tests; no current exploitability claim is made.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-118",
          "title": "Guest error handling lost uncertain outcomes",
          "text": "Within a guest, the runner could discard a structured gateway error and report a known failure even when provider acceptance was uncertain. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-119",
          "title": "Budget-refusal handling was unreachable",
          "text": "The adapter's dedicated budget-refusal behavior did not run with the pinned runner. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-120",
          "title": "Concurrent consultations exceeded a token grant",
          "text": "Concurrent admissions for the same consultation could each pass its token limit, allowing the combined usage to exceed the grant. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-121",
          "title": "Authorized members could not decide approvals",
          "text": "A project member with the project role that permits it could not decide an approval on a session they were authorized to act on. As of 30 September 2026 the authorization defect remains marked fixed in tests; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-122",
          "title": "Onboarding offered unavailable managed inference",
          "text": "The onboarding flow allowed selection of managed inference even though the service reported it unavailable. The defect is marked fixed in tests; customer-supplied provider keys remain required.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-123",
          "title": "Jobs accepted disabled provider keys",
          "text": "A Cruise job could be accepted even when its only key for a required provider was disabled. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-124",
          "title": "Advice delivered to a paused session",
          "text": "A consultation could be delivered to an adviser whose session was parked or being saved. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-125",
          "title": "Advice accepted for a removed adviser",
          "text": "A consultation could be accepted after the adviser had been removed. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-126",
          "title": "Advice questions were attributed as user instructions",
          "text": "An adviser's conversation displayed another agent's question as if a person had issued it. The attribution defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-127",
          "title": "Candidate code could influence verification results",
          "text": "A candidate could alter the verification process so that incorrect work was accepted. This specific defect is marked fixed in tests; a broader open test-report integrity issue remains separately listed.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-128",
          "title": "A paid test did not reliably enforce its spending stop",
          "text": "A paid test's spending limit used unapproved pricing and did not check continuously during each case. The test defect is marked fixed in tests; it does not establish a customer spending guarantee.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-129",
          "title": "A paid test overstated its prerequisites",
          "text": "A paid test authorization could claim a verified provider limit without one and did not require an earlier keyless check. The evidence-quality defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-130",
          "title": "The service did not control the selected model",
          "text": "The service did not select the model called by the runner inside the machine. The missing control is marked fixed in production on 30 September 2026.",
          "status": "fixed-in-production",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-131",
          "title": "Some required test cases could not run",
          "text": "Three cases in a private test suite could not run against the then-current candidate. The coverage defect is marked fixed in tests, without proving those earlier cases passed.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-132",
          "title": "Readiness and retry checks used invalid assumptions",
          "text": "A test checked readiness before its prerequisite and retried by reusing a prior submission. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-133",
          "title": "Candidate code could replace the final test report",
          "text": "A candidate that had not fixed the problem could replace its final report and be accepted. This specific defect is marked fixed in tests; the broader report-integrity limit remains open.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-134",
          "title": "Code under test can falsify its own report",
          "text": "The source retains an open high-severity issue in which code under test can fabricate a consistent report from inside the runner. A passing report alone does not independently prove that the work is correct. As of 30 September 2026 the issue remains open.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: high. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-135",
          "title": "Verification ran customer code with excessive host privilege",
          "text": "The source reports that verification ran customer project code with excessive privilege on the host. This critical isolation issue is marked fixed in tests on 26 September 2026; that status is not a production certification.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: critical. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-136",
          "title": "Task lists silently omitted later records",
          "text": "The task list stopped after 200 records without indicating that more existed. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-137",
          "title": "Deleting a session did not stop its machine",
          "text": "Session deletion promised to stop its machine but did not do so. The finding is marked fixed in tests; a separate dated agent-session production test also records successful stop and deletion for its single tested session.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-138",
          "title": "Records within one second may sort incorrectly",
          "text": "Time values stored as text could order records written within the same second incorrectly. On 1 October 2026 the source changed this finding to fixed in tests, with every stored time now written in one fixed-width form and a one-time migration for existing records; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 26 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-139",
          "title": "Permission tests expected nonexistent output fields",
          "text": "A permission test looked for field names that the client did not produce. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-140",
          "title": "Accepted numeric input was refused later",
          "text": "Some valid numeric representations were accepted at job intake but then refused by the worker. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-141",
          "title": "Denied verification tampering was not recorded",
          "text": "Attempts to alter protected verification inputs could be denied by the sandbox yet accepted without recording the attempt. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-142",
          "title": "A test contaminated its own clean build inputs",
          "text": "A test wrote generated files into a candidate that was required to remain clean, preventing its image build. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-143",
          "title": "Leftover evidence was mistaken for current execution",
          "text": "A test treated another test case's leftover marker as proof that a tool was currently running. The false-positive defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-144",
          "title": "An instruction after approval was not acknowledged",
          "text": "An instruction submitted immediately after an approved tool turn could receive no acknowledgement and make no model call. On 30 September 2026 the source closed this finding as environmental: the stall was caused by a credit safeguard in the test environment pausing the session, and the same sequence then passed in later certified runs.",
          "status": "closed",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: closed. Earlier recorded status: open on 26 September 2026.",
          "limitation": "Recorded severity: high. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-145",
          "title": "Tool-running and retry checks were unreliable",
          "text": "A test inferred tool execution from a transient activity label and reused a fixed submission identity on retry. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-146",
          "title": "An executing tool had the wrong activity label",
          "text": "During an approved tool operation, the displayed activity said general work rather than tool execution. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-147",
          "title": "Provider keys could become unusable during a job",
          "text": "Required provider keys were checked only when the job was submitted, so later stages could fail after earlier model calls had already incurred usage. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-148",
          "title": "Permission decisions outlived the request waiting for them",
          "text": "A permission decision could still be claimed after the runner had stopped waiting for it. The effects-accounting defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-149",
          "title": "Test credit exhaustion interrupted the intended scenario",
          "text": "A test account lacked the credit needed for the planned run, so the funds control parked its machine mid-test. The test-setup defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-150",
          "title": "Credit-paused sessions still appeared running",
          "text": "After the funds control parked a session, it still appeared to be running and related views did not identify the funds pause. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-151",
          "title": "Tests could not distinguish a stopped machine from an unresponsive runner",
          "text": "A test lacked the evidence needed to distinguish machine shutdown from a runner that stopped answering. The diagnostic defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-152",
          "title": "The first task after pause and wake failed",
          "text": "After pause and wake, the first instruction failed because its recorded execution generation had changed. Pausing an idle adapter also waited unnecessarily. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-153",
          "title": "A previous failed test left later retries held",
          "text": "A test retried behind a queue hold left by its own failed attempt, invalidating the later measurement. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-154",
          "title": "A crashed test was reported as successful",
          "text": "A test wrapper reported success after its scenario crashed; a related case also failed while reading the client's task count. The false-positive defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-155",
          "title": "An advice test inspected the wrong request",
          "text": "A consultation test examined the wrong request and failed without retaining enough evidence to diagnose the result. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-156",
          "title": "Releasing an uncertainty hold did not restore a worker",
          "text": "After uncertain acceptance, the adapter could stop permanently, so an authorized release of the hold reached no worker. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-157",
          "title": "A stalled earlier task invalidated later tests",
          "text": "A test evaluated later cases while the adapter was stuck on an earlier closed task, and its diagnostic capture could not show that state. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-158",
          "title": "An interrupted test left a closed task active",
          "text": "A test passed an interruption even though the adapter still held the closed task; its evidence parser also misread lists of open tools. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-159",
          "title": "Unpriced earlier attempts prevented job resume",
          "text": "A Cruise job could not resume if earlier attempts had no recorded price. The defect is marked fixed in tests, but that does not establish an effective spending ceiling for unpriced usage.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-160",
          "title": "Unpriced Cruise usage has no effective spending ceiling",
          "text": "While model costs are unavailable, a Cruise job's spending ceiling does not constrain it; the attempts limit is a separate bound. As of 30 September 2026 this high-severity money-related issue remains open: pricing support was prepared but stays inactive until model rates are ratified.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: high. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-161",
          "title": "Verification used files a candidate had removed",
          "text": "Verification could use files that the candidate had deleted, so the tested result did not match the candidate's final contents. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-162",
          "title": "A wake test required readiness too early",
          "text": "A test required readiness after wake before the next instruction, although the supported sequence did not provide it then. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-163",
          "title": "A task test omitted the outcome it claimed",
          "text": "A test marked a task successful without supplying the outcome required by its own evidence contract. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-164",
          "title": "Help-output ordering made a test unstable",
          "text": "A command's flag list appeared in unpredictable order, causing a test to pass or fail by chance. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-165",
          "title": "Several lists silently stopped after their first page",
          "text": "Session, agent, approval and proposal lists did not reliably offer later pages or indicate that additional records existed. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-166",
          "title": "Request references could not be traced",
          "text": "Response request references were created too late to be sent through or logged with the underlying operation, making them unusable for tracing. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-170",
          "title": "Agent-session refusals were not reachable through customer identifiers",
          "text": "The customer-visible session identifier did not reach the intended refusal for unsupported shell access, and older session routes returned not found. The routing defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-171",
          "title": "Older session operations bypassed agent supervision",
          "text": "Older stop, resume and fork operations could reach an agent session without its normal supervision. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-172",
          "title": "Concurrent distinct requests were unnecessarily refused",
          "text": "Request admission did not provide its documented atomic behavior, causing concurrent distinct requests to be refused. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-173",
          "title": "Late consultation replies were accepted",
          "text": "A reply arriving after the consultation deadline could still be accepted as advice. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-174",
          "title": "Host storage exhaustion stopped a restored session",
          "text": "A restored session stopped answering after another session was provisioned because host storage ran out. The environmental finding is closed with a guard recorded; it is not a general availability guarantee.",
          "status": "closed",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: high. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-175",
          "title": "New session network identities were not checked for collisions",
          "text": "Provisioning did not check a new session's network identity against existing sessions on the same host. The defect is marked fixed in tests on 26 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-26",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-180",
          "title": "A retry replayed the previous task",
          "text": "A test retried the same instruction through the live view and received the prior task rather than a fresh attempt. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-181",
          "title": "A new-adviser test used invalid readiness and retry assumptions",
          "text": "A test required a new adviser to be ready before its first instruction and reused its name on retry. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-182",
          "title": "A consultation test passed without an advice turn",
          "text": "A test asked for consultation from an agent that could no longer take work and accepted a result without an actual advice turn. The false-positive defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-183",
          "title": "A paid test confused exhausted budget with advice failure",
          "text": "A paid run spent its shared token allowance before a later consultation case and interpreted the resulting refusals as consultation or reply defects. The test defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-184",
          "title": "Tools could alter the runner's control configuration",
          "text": "Tools and the runner shared an identity that allowed tools to change control configuration during execution. The isolation defect is marked fixed in tests on 27 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-27",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-185",
          "title": "Customer-key attribution was missing",
          "text": "Usage admission could report no key source even though the session was bound to a customer-supplied key. The attribution defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-27",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-186",
          "title": "Consultation payer and spending were not recorded",
          "text": "The service did not record who paid for a consultation, and spending attributed to advice could not be queried. The money-related defect is marked fixed in tests on 27 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-27",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-187",
          "title": "Three tests lacked a negative control",
          "text": "Three test gates lacked a deliberately failing control, limiting the evidence that they would detect incorrect behavior. The coverage issue remains open.",
          "status": "open",
          "date": "2026-09-27",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-188",
          "title": "Advice-call attribution did not reach payment views",
          "text": "Per-call advice attribution did not reach the control plane, and payment views still described the capability as unavailable. The defect is marked fixed in tests on 27 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-27",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-189",
          "title": "Provisioning showed misleading readiness guidance",
          "text": "A newly provisioned agent told the user to wait for readiness, although the supported runner could not become ready before its first instruction. The defect is marked fixed in tests.",
          "status": "fixed-in-test",
          "date": "2026-09-28",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-190",
          "title": "New agent sessions lacked a bound provider key",
          "text": "The client could create an agent session without binding a provider key, causing its first instruction to fail. The defect is marked fixed in tests on 28 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-28",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-191",
          "title": "Idle agents always appeared stale",
          "text": "The client always labeled an idle agent stale, making the status misleading. The defect is marked fixed in tests on 29 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-29",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-192",
          "title": "Metered model calls were absent from customer usage",
          "text": "A model call counted by the gateway was missing from the customer usage view. The finding is marked fixed in tests; the register separately says admission for agent-session calls is unverified.",
          "status": "fixed-in-test",
          "date": "2026-09-29",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-193",
          "title": "Two token limits govern different call paths",
          "text": "The gateway budget constrained model calls from a session's machine, while a separate session cap applied only to service-originated calls. On 30 September 2026 the source changed this finding to fixed in tests, with each session now governed by one token budget fixed when it is provisioned; a test fix is not a production fix.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test. Earlier recorded status: open on 29 September 2026.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-194",
          "title": "Agent tools ran without the promised separate unprivileged user",
          "text": "Inside a session machine, an agent's runner and every tool it started ran with the privileges of the agent's controlling process instead of as a separate unprivileged user, although the published capability statement described that separation. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-195",
          "title": "Free-tier limits were not applied to agent sessions from the newer API",
          "text": "Agent sessions provisioned through the newer API received the paid-tier token budget whatever the account's tier, and the free tier's one-running-session limit and capacity cap were not applied. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-196",
          "title": "Session runtime billing could include time a session was parked",
          "text": "The engine's runtime meter measured from a session's first event to its last and ignored the statement window, so time a session spent parked before a later wake could be billed as runtime. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-197",
          "title": "A funds pause could record a stopping state that was never measured",
          "text": "When a session was paused because funds ran out and the service could not read back the engine's answer, the session record showed it as stopping although that state had not been measured. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-198",
          "title": "Approval actions were not tied to the agent that asked",
          "text": "Claiming, answering or abandoning a permission request did not check that the caller was the agent, session and account the request belonged to, so a holder of service credentials, including code inside another session, could act on an approval it did not own. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-199",
          "title": "Advice after a failed wake named a check that did not re-measure",
          "text": "When a wake could not read back the session's state, the answer told the customer to check again with the session status command, but the stored session record was never measured again, so other readers kept seeing an unavailable state. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-200",
          "title": "Forking a running session could put the child's credential in the parent",
          "text": "With signed capabilities enabled, forking a running session wrote the new child's signed capability into the parent session's machine, and the child kept the parent's stale one. The source records that this mode was not enabled in production at the time. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-201",
          "title": "Resume and kill could signal an unrelated process reusing a stored id",
          "text": "Resume and kill checked only that a stored process id was alive before signalling it, so after a host restart a reused id could lead to an unrelated process being killed. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-202",
          "title": "Regression guards relied on a copied signing key and hand-built credentials",
          "text": "Three regression guards started a test engine with a key setting it ignored, minted credentials with hand-written code instead of the product's own, and handled a copy of a signing key unsafely on the test machine. The defect is marked fixed in tests on 30 September 2026.",
          "status": "fixed-in-test",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-203",
          "title": "Disk space held by parked sessions was never reclaimed",
          "text": "No scheduled job reclaimed the rebuildable disk space held by parked sessions, so that space was never freed. A scheduled cleanup with its own monitor was added. The defect is marked fixed in production on 7 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-07",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-204",
          "title": "Two engine checks left network resources behind after their runs",
          "text": "Two engine checks did not force-delete their sessions or remove fork network resources, leaving them on the test machine where they later made another check's preflight fail. Amendments were drafted but not applied. The issue remains open.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-205",
          "title": "An engine gateway check had three assertions that always passed",
          "text": "Three assertions in the engine gateway check passed whichever outcome they observed, so they gave no assurance. An amendment making each able to fail was drafted but not applied. The issue remains open.",
          "status": "open",
          "date": "2026-09-30",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-206",
          "title": "Checkpoint soak sabotage run could report green on no evidence",
          "text": "The sabotage run of the long checkpoint soak check fell back to a missing record when its own short soak wrote nothing, and could then report a green result on no evidence. The finding is closed on 12 October 2026: the fallback was removed, and a later sabotage run judged its own record and caught the sabotage as intended.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-207",
          "title": "Two regression tests were not run by any automated check",
          "text": "Two named regression tests, one for the verifier's refusal handling and one for the image builder's refusals, were run by nothing, so they gave no protection. The finding is closed on 1 October 2026: both now run in continuous integration and each was shown able to fail; it concerned only the test process, with no product exposure.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-208",
          "title": "An interrupted image build left a partial file that blocked bench checks",
          "text": "When copying a published machine image failed partway, the image build left a partial file among the preserved images, and every check whose preflight ran the health check on the test machine then stopped before its first assertion. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-209",
          "title": "Checkpoints could not be restored on an engine without the base image",
          "text": "After a change that compares the saved software stack at restore, a checkpoint could no longer be revived on a second engine holding only its stored content and not the base image, so a portable restore was refused. The restore now proceeds and reports compatibility as unknown. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-210",
          "title": "Restore check sampled its baseline on a fixed timer",
          "text": "One part of the portable restore check read its baseline a fixed 3 seconds after boot, so a slow first line from the test machine produced a failure on missing evidence instead of an abort. An amendment that waits for the line was drafted but not applied. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-211",
          "title": "Deleting a session did not delete its checkpoint content",
          "text": "Deleting a session removed its records, but the content of its checkpoints stayed readable with the account's key until the whole account was deleted, although the retention policy said checkpoint content was deletable per session. The source records that sessions saved in the older format still await conversion. The defect is marked fixed in production on 6 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-212",
          "title": "Account deletion did not purge content from the optional resume cache",
          "text": "With an optional resume cache turned on, deleting an account did not purge that cache, so decompressed content from the account's checkpoints could remain on the host. The cache was off by default. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-213",
          "title": "Account data keys were kept separately on each host",
          "text": "Each host kept its own copy of an account's data key while failover shared the store, so a second host could not read an encrypted session or could create a different key, and deleting an account on one host could leave a key on another. The second host was not running at the time. The defect is marked fixed in production on 6 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-214",
          "title": "Encrypted checkpoints had no long-running soak check",
          "text": "The long-running checkpoint checks exercised only unencrypted sessions, so the encrypted configuration used in production had a round-trip record but no soak. An encrypted soak check was added and passed a three-hour run. The defect is marked fixed in tests on 5 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-05",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-215",
          "title": "Regression harness exit code ignored failures in later sections",
          "text": "The regression harness decided its exit code before its later sections ran, so a failure in any of those sections was printed but the run still reported success. The finding is closed on 1 October 2026: it concerned only the test harness, with no product exposure, and the exit code now reflects every section.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: high. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-216",
          "title": "Agent commands on a forked session reached the parent session",
          "text": "Starting, reading or stopping an agent on a forked session sent the commands to the parent session's machine instead of the child's. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-217",
          "title": "A fixed timing bound made a resume unit test fail under load",
          "text": "A unit test used a fixed 150 millisecond bound that a busy disk could exceed, so it failed intermittently on a loaded machine. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-218",
          "title": "Payment events could grant credit without a verified paid order",
          "text": "The payment webhook would have granted credit on a checkout update without checking that it was paid, and could grant a paid checkout twice, while a refund-created event netted nothing; checkout update events were not subscribed at the time. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-219",
          "title": "Resuming through the newer API bypassed the free-tier session limit",
          "text": "A free-tier account could run two sessions at once by resuming a second one through the newer API, which lacked the one-session limit the older route applied. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-220",
          "title": "Console sessions defaulted to the free-tier budget for paid accounts",
          "text": "Sessions started from the console defaulted to a 500,000 token budget for every account, although paid tiers default to 2,000,000 tokens. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-221",
          "title": "Billing reconciliation monitor could alert on normal settlement lag",
          "text": "After a billing change, the internal reconciliation monitor could flag an account whose usage briefly exceeded its balance before the funds pause took effect, which is expected settlement lag. The monitor now tolerates that lag within set bounds. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-222",
          "title": "Free-tier session limit was skipped when the engine could not be read",
          "text": "When the engine's list of running sessions or its session count could not be read, the free tier's one-session limit and capacity cap were not applied, so a start could proceed unchecked. Such starts are now refused with a retryable error. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-223",
          "title": "Project members saw the gateway usage figure as unreadable",
          "text": "In the usage view, a member of the project that holds a session saw the gateway meter as unreadable, because it was read under the member's account instead of the session's own account. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-224",
          "title": "Permission request details were readable across accounts",
          "text": "Any holder of service credentials, including code inside a session of another account, could read any permission request by its id, including its arguments and decision. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-225",
          "title": "Code in one session could act on another session's tasks",
          "text": "Code inside one session could act for another session's agent in the same account: finishing or acknowledging its tasks, posting its results, answering its consultations and spending its reserved budget. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-226",
          "title": "Permission requests could be raised for another session or agent",
          "text": "Code inside a session could raise a permission request in another session of the same account, or attributed to an agent that never asked. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-227",
          "title": "Pending tasks lacked structured fields naming what held them",
          "text": "The pending task view described why a held task was waiting only in a text reason, without the hold and blocking task identifiers the task view already provided. Both fields were added. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-228",
          "title": "Failed account deletion could leave sessions behind with no retry",
          "text": "When a customer deleted their account and the engine's erase step failed, the account was already closed and its key destroyed, so its sessions and per-account engine key could be left behind and the customer could not retry the deletion. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-229",
          "title": "Release check cleanup removed test data whatever the deletion result",
          "text": "A release check's cleanup removed its bystander test account's data directly from the database even when the service's deletion route had not confirmed the deletion, which could hide a failed deletion. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-230",
          "title": "Admin overview could wait up to a minute on a hanging engine",
          "text": "The admin console's overview asked the engine for its health on every load and could wait up to a minute when the engine hung, and its fleet tile could disagree with the public status feed. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-231",
          "title": "Attach on Windows did not switch the terminal to raw mode",
          "text": "On Windows, ks attach relied on a Unix terminal tool to switch the terminal into raw mode, so an attached session ran in line-buffered (cooked) mode there. The defect is marked fixed in tests on 1 October 2026, in an unreleased client build that has not yet run on a real Windows console.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-232",
          "title": "Windows client not yet run on a real Windows machine",
          "text": "The Windows build of the ks client has been checked only by an automated build job that runs a subset of its tests; no part of it has run on a real Windows machine, so its behavior there is not established. As of 1 October 2026 the issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-233",
          "title": "Test harness could act on the hosted service when signed in",
          "text": "Some test-harness checks that run ks commands used whatever account the client on the test machine was signed in to, so with a hosted login present they could have started, stopped or metered sessions on the hosted service. The finding is closed on 1 October 2026: it concerned only the test harness, which now refuses to run while signed in.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-234",
          "title": "Launch rehearsal could leave the host on the rehearsal's engine process",
          "text": "The pre-launch rehearsal did not stop one engine process it had started, so afterwards the host could keep serving from the rehearsal's process instead of the production service. The finding is closed on 12 October 2026: the rehearsal was replaced by one that runs beside production with its own separate processes.",
          "status": "closed",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-235",
          "title": "Published-claims check did not run on every change",
          "text": "The check that every published claim cites an existing, sealed test result ran only when a release check called it, so a claim citing a missing result could go unnoticed between runs. The finding is closed on 1 October 2026: it concerned only the build checks, which now run this check on every change.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-236",
          "title": "Many release checks do not declare the kind of claim they prove",
          "text": "A rule requires every release check to state whether it proves a point-in-time or an ongoing property, but about half of the check scripts declare neither. A lint now stops new undeclared checks; the existing declarations are still owed, and as of 12 October 2026 the issue remains open.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-237",
          "title": "Engine kill-cycle check could pass with no model call",
          "text": "A release check of the engine's kill-and-resume cycle counted an agent cycle as passing without any model call being made, and whether it spent money depended on the test machine's gateway. As of 12 October 2026 a correction has been drafted but not applied, and the issue remains open.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-238",
          "title": "A Cruise check overstated request counts in failure messages",
          "text": "A Cruise release check kept counting requests after it reset its test stub, so its failure messages reported more requests than were made. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-239",
          "title": "A release check reported setup failures as failed assertions",
          "text": "A release check counted any failure of its scenario, including a failure to set the scenario up, as a failed assertion, so a broken setup read as a product failure instead of an aborted run. As of 12 October 2026 a correction has been drafted but not applied, and the issue remains open.",
          "status": "open",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-240",
          "title": "Engine harness checks left network devices behind on the test machine",
          "text": "Three engine test-harness checks stopped their virtual machines without deleting their sessions, leaving network devices and data behind on the test machine. The finding is closed on 1 October 2026: it concerned only the test harness, whose checks now delete what they create and confirm nothing is left.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-241",
          "title": "A failed checkpoint could leave a session paused but shown as running",
          "text": "A checkpoint whose pause step timed out could end without taking the snapshot and leave the session's virtual machine paused while its record still read running. The engine now resumes and confirms the machine after any failed checkpoint; the defect is marked fixed in tests on 6 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-242",
          "title": "Engine could delete leftover database files that may hold usage records",
          "text": "When the engine's database file was removed while it ran, the engine deleted leftover journal files that could hold gateway usage records used for billing, instead of setting them aside, and several requests could reopen the database at once. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-243",
          "title": "Cruise job build record did not cover all worker code",
          "text": "The worker build a Cruise job records covered only one file of the worker, so changes to the other code the worker runs left the recorded build unchanged. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-244",
          "title": "Resumed Cruise job could restart from its first step",
          "text": "In production, a resumed Cruise job could start again from its first step with nothing counted as already spent when it resumed on a worker host without its earlier local record. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-245",
          "title": "Price-change check would ignore changes to per-model rates",
          "text": "The check that marks money-related release checks stale after a price change did not watch the per-model rate book, so a future change to ratified rates would not have required those checks to re-run. It was dormant while the rates are unratified; the defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-246",
          "title": "Dollar budget rule would round small per-token rates up",
          "text": "The rule for reserving a dollar budget before a call could not express a rate below one micro-dollar per token, so ratified per-million rates would have been rounded up and a dollar limit could refuse calls it had room for. It is dormant while dollar admission is unavailable; the defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-247",
          "title": "Internal record misdescribed how Cruise attempts are metered",
          "text": "An internal finding record said each Cruise attempt is metered from the parent session's usage, when each attempt is metered on its own fork's gateway usage. The finding is closed on 1 October 2026: the record was corrected and no product behavior changed.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-248",
          "title": "Cruise check passed only after a manual re-signing step",
          "text": "A Cruise release check verified a committed test fixture signed with a key no run holds, so it could pass only after a manual re-signing that no run can do. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-249",
          "title": "Adapter supervisor dropped settings meant for the agent adapter",
          "text": "When run under its supervisor, the agent adapter received only some of its settings: 16 of the 30 it acts on, such as log format and approval timing, were dropped. The engine passed none of the dropped settings, so the effect was latent; the defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-250",
          "title": "Limits page misdescribed unanswered approval requests",
          "text": "The published Limits page said an unanswered approval request stays pending, but since 22 September 2026 an unanswered request is closed when its window ends and a later decision is refused. The page source was corrected, and the defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-251",
          "title": "Certification harnesses wrote where the agent runner has no access",
          "text": "Certification test harnesses had the agent runner write files under the administrator's home folder, which fails now that the runner runs as a separate, unprivileged user. The finding is closed on 1 October 2026: it concerned only the test harness, which now writes under the runner's own home.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-252",
          "title": "Interrupted image publish could leave partial files behind",
          "text": "If publishing a new session image was killed or the host crashed partway, a partial copy or an image without its marker could be left in the preserved image store. The defect is marked fixed in tests on 1 October 2026; one narrow interruption point is completed by the next build.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-253",
          "title": "Commit checks on side branches ran the main branch's version",
          "text": "Developer commit checks in every working copy ran the main branch's version of the check, so a check changed on main could refuse commits on branches that did not yet carry its scripts. The finding is closed on 1 October 2026: it concerned only developer tooling.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-254",
          "title": "Forked session traffic was misaddressed for up to 40 seconds",
          "text": "After a fork, the child session's own outbound traffic, gateway calls included, went to the wrong network address for about 15 to 40 seconds until it re-learned the address, because the host side of each session's network link got a random hardware address. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-255",
          "title": "Cancelled Cruise job could leak its parked parent session",
          "text": "A Cruise job's parked parent session was known only to the worker host that parked it, so a resume on another host built a new parent and a cancel there left the old one stored and unused. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-256",
          "title": "Cruise test stand-in handled cancellations unlike production",
          "text": "The test stand-in for the service handed a cancelled Cruise job back to the worker, while production lists it for teardown, so a Cruise release check proved a path production does not take. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-257",
          "title": "Cruise job build record did not cover model and rate tables",
          "text": "The worker build a Cruise job records covered the worker's code but not the model catalogue and rate book it reads, so a change to either left the recorded build unchanged. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-258",
          "title": "Approval unit test failed intermittently under load",
          "text": "A unit test of approval requests whose hook had gone failed intermittently under load, because it closed the hook before the adapter knew the request's id. The test was corrected and the defect is marked fixed in tests on 1 October 2026; the underlying timing case in the product was proposed as a separate finding.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-259",
          "title": "Admin account view always showed no device tokens",
          "text": "The admin console's account view always showed an empty device-token list because its query named a column that does not exist, and a failed list read was shown as empty. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-260",
          "title": "Monitor incidents could sort slightly out of order on the status feed",
          "text": "The billing reconciliation monitor stamped the incidents it opened in whole seconds, so on the public status feed and admin incident list they could sort a fraction of a second out of order against the service's other incidents. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-261",
          "title": "Encrypted sessions never resumed warm and could leave plain copies",
          "text": "For sessions with stored-data encryption on, the resume cache could never serve an entry, so they always resumed cold, and with optional cache population turned on it wrote decrypted copies of their data to the host's disk. Encrypted stores now bypass the cache; the defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-262",
          "title": "Engine and gateway could set aside each other's live database files",
          "text": "When the shared session database was missing, the engine and the gateway could each set aside its leftover files at the same moment, so one could move the other's live files and session or usage records could become invisible. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-263",
          "title": "Agent image publishing was not safe against an interrupted run",
          "text": "If the step that publishes the agent environment image was interrupted, the service could be left with a partial image copy or an image without its integrity marker, and a later run would not repair it. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-264",
          "title": "On Windows the client showed a pasted key while adding it",
          "text": "On Windows, adding a provider key with the client could not hide the pasted key on screen, and the client also could not save terminal settings or read the window width there. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-265",
          "title": "Attaching from a Windows console could print raw escape codes",
          "text": "On some Windows consoles, attaching to a session did not turn on terminal escape processing, so the session's formatting codes could print as raw characters; this was not confirmed on a real Windows console. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-266",
          "title": "A member's agent service could act in another account's session",
          "text": "Within a shared project, an agent service acting for one account could raise an approval question or reserve spending in a session owned by another account, with the record kept under the wrong account. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-267",
          "title": "Another account could close or read an adviser consultation",
          "text": "A caller acting for another account could close a pending or late adviser consultation, or read back an answered one, because the account check ran after those steps. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-268",
          "title": "Billing monitor would flag a false stall when usage starts after idle",
          "text": "With a pending usage accounting change, the monitor that checks usage is settled would have read any account that starts using the service after a quiet period as stalled and raised a major incident until the next settlement cycle ran. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-269",
          "title": "A partial refund removed the whole purchased credit",
          "text": "A partial refund of a credit purchase removed all the credit the order had granted, and a refund that later failed did not give the credit back. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-270",
          "title": "Account deletion page said sessions were kept when they were erased",
          "text": "After deleting an account, the confirmation page said running sessions had been parked at a checkpoint, when in fact every session was erased and its checkpoints made unreadable, so the page suggested work had been kept. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-271",
          "title": "A service test failed rarely on random identifiers",
          "text": "An automated test of the service failed in about 0.03% of runs when a randomly generated identifier happened to contain a number the test treated as a leak; there was no product impact. The finding is closed on 1 October 2026 because it concerned only the test, which was corrected.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-272",
          "title": "Older session creation used fixed budget figures, not the price list",
          "text": "Creating a session through the older interface used built-in default budget figures instead of reading the published price list; the figures matched at the time, but a price list change would not have reached these sessions. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-273",
          "title": "An approval could stay open after the agent stopped waiting for it",
          "text": "If the agent's permission request went away while its approval question was being raised, the question stayed open and could be approved for an action that would never run, until it expired. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-274",
          "title": "Test bench cleanup checks missed leftover processes",
          "text": "The test bench's cleanup checks did not list leftover processes still holding the product's isolated networks, so a run could report a clean teardown when something was left behind. The finding is closed on 1 October 2026 because it concerned only the test harness.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-275",
          "title": "Bench test drivers looked for the wrong file names",
          "text": "Two test bench drivers looked for files under names the scripted test service never wrote, so one check of a denied action could pass on missing evidence. The finding is closed on 1 October 2026 because it concerned only the test harness.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-276",
          "title": "Storage held by a failed Cruise job was never released",
          "text": "When a Cruise job failed, the parked session it kept for resuming was never released, and the promised seven-day expiry was not implemented, so that storage could be held indefinitely. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-277",
          "title": "Cruise jobs on several engines could leave parked sessions behind",
          "text": "When the service runs more than one engine, a Cruise job's parked session on one engine could neither be reused nor cleaned up by a worker on another engine, and one engine's cleanup could end cleanup on the others. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-278",
          "title": "Simulated Cruise service recorded events production never records",
          "text": "A simulated control service used in Cruise tests recorded events the real worker never sends and accepted verdicts the real service refuses, so tests run on it could read a job history that differs from production. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-279",
          "title": "Two Cruise test modules failed when run in one process",
          "text": "One Cruise test left its temporary settings in place after finishing, so another test failed when both ran in the same process; automated checks were not affected and there was no product impact. The finding is closed on 1 October 2026 because it concerned only the tests.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-280",
          "title": "A Cruise acceptance check could not pass with current clients",
          "text": "Since client version 0.1.13, one Cruise acceptance check could not pass with any client, because its simulated service did not answer the model catalog and key list requests the approve step now makes. The finding is closed on 4 October 2026 after the check was amended and passed.",
          "status": "closed",
          "date": "2026-10-04",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: high. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-281",
          "title": "A billing safety check no longer matched the duplicate charge rule",
          "text": "A billing safety check and the usage meter report counted duplicates by request rather than by attempt, which no longer matched the rule the database enforces, so the check failed and could not tell a real double charge from a legitimate repeat. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-282",
          "title": "Admin and activation test scenarios could reach a previous server",
          "text": "Several admin console and automatic activation test scenarios restarted the control service on the same port while the previous one was still shutting down, so a run could reach the old service and its result could not be trusted. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-283",
          "title": "Two release checks leave a network device behind on each run",
          "text": "Two release checks leave one virtual network device behind on the test bench each time they run, because their cleanup does not remove what they create. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-284",
          "title": "A retried call after resume could be run and billed twice",
          "text": "From 20 September to 6 October 2026, if a session was paused while a model call was in flight and its answer had already been sent, the retry after resume was run again and billed again, so a customer could pay the provider twice on their own key and be metered twice; the source states this applied to the production service. The defect is marked fixed in production on 13 October 2026: the fix has been in the production gateway since 6 October 2026, and the paid gateway test re-ran green on 13 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-13",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production. Earlier recorded status: fixed-in-test on 13 October 2026.",
          "limitation": "Recorded severity: critical. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-285",
          "title": "Repeated identical requests could be answered from storage unbilled",
          "text": "After one lost reply was replayed, every later identical request in that session was answered from the stored reply instead of being run, so new work was neither performed nor billed and could return an old answer. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-286",
          "title": "A delivery failure record was saved where the retry check never looked",
          "text": "When sending an answer failed partway through, the record of that failure was saved under a different key from the one the retry decision reads, so the retry decision never saw it. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-287",
          "title": "A session start test failed when a random id matched a pattern",
          "text": "An automated test occasionally failed when a randomly generated session identifier happened to contain a number the test treated as a leak; there was no product impact. The finding is closed on 1 October 2026 because it concerned only the test, which was corrected.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: low. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-288",
          "title": "A resumed session's machine once failed to connect its network",
          "text": "In one test run, a resumed session's virtual machine never connected to its network device, and the cause was not established. The finding is closed on 5 October 2026 because it was not reproduced in more than 450 further resumes, and a permanent check was added.",
          "status": "closed",
          "date": "2026-10-05",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-289",
          "title": "A forked session's network address could change after setup",
          "text": "For a forked session, the host could replace the hardware address of its network link after the session's network had already learned it, which could disrupt the forked session's connectivity; this was not observed. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-290",
          "title": "The test bench clock was adjusted by two competing time services",
          "text": "The test machine's clock ran fast and was stepped back every ten seconds because two time services adjusted it, making timing on the bench unreliable; there was no product exposure. The finding is closed on 1 October 2026 because it concerned only the test bench configuration, which was corrected.",
          "status": "closed",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: closed.",
          "limitation": "Recorded severity: medium. Closure applies to this recorded case, not every workload.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-291",
          "title": "Forked sessions could be corrupted when host memory ran low",
          "text": "When the host ran short of memory, restoring several forked sessions in turn could corrupt the memory of children already running, causing them to hang or crash. The defect is marked fixed in production on 6 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-292",
          "title": "Cruise and setup screen budgets used fixed figures, not the price list",
          "text": "Cruise job sessions used built-in budget figures instead of the published price list, and the onboarding setup screen showed every account the paid tier budget, so a free account was shown four times the budget its session received. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-293",
          "title": "The price consistency check treated test files as prices",
          "text": "An internal check that keeps prices in one source flagged durations in test files as prices, so a pre-release check failed while automated checks passed; there was no product impact. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-294",
          "title": "The link on the account deletion page did not work",
          "text": "After deleting an account, the link on the confirmation page pointed to a broken address on the service instead of the KeepState website. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-295",
          "title": "A fleet test checks a fixed free budget, not the price list",
          "text": "One fleet acceptance test checks a fixed free tier budget figure instead of the figure in the price list, so it would fail if the free budget were lowered, even with correct service behavior. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-296",
          "title": "An interrupted deploy could leave an agent image the engine cannot use",
          "text": "If a deploy was interrupted while publishing an agent image, the image could be left without its description file, and later deploys reported it as already built without repairing it, so the engine could not start agents from it. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-297",
          "title": "Cruise sessions could run on a guessed token budget when none was given",
          "text": "When a Cruise job's claim carried no token budget, its sessions ran on a fixed fallback budget instead of the price book figure for the account's tier; such a claim is now refused before any session starts. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-298",
          "title": "A permission request could stay open after its reply was lost",
          "text": "If an agent's permission request reached the service but the reply was lost in transit, the tool call was refused yet the request stayed open and decidable until its time limit, with nothing able to close it. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-299",
          "title": "No notification was sent when a Cruise job moved to review",
          "text": "A published claim said a Cruise job whose attempts were exhausted reached the review queue with a notification, but no part of the service sent or recorded one. The service now emails the account and records the notification, or records why it was not sent. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-300",
          "title": "A failed Cruise job did not say why it failed",
          "text": "When a Cruise job failed, the reason was not passed to the service, so the failure record a customer reads carried no error, contrary to the documented behavior. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-301",
          "title": "Cruise job status showed an empty reason for jobs in review",
          "text": "The status of a Cruise job waiting for review always reported an empty review reason, because it read a field the service never records. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-302",
          "title": "A Cruise test stand-in accepted attempt changes the service refuses",
          "text": "The simulated control plane used in Cruise tests kept and accepted attempt data the real service does not, including changes after a job had stopped, so one test check read a value the service never stores. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-303",
          "title": "Evidence sessions kept by failed Cruise jobs were never released",
          "text": "Sessions that a failed Cruise job kept parked as evidence were never released, so they stayed parked after the job had ended. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-304",
          "title": "The Cruise runner recorded a parent released when its deletion failed",
          "text": "When deleting a Cruise job's parked parent session failed at acceptance, the runner's own record still said the parent was released while the session stayed parked; the service's release listing was not affected. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-305",
          "title": "A production check's cleanup could leave a job's parent session behind",
          "text": "The cleanup step of one production Cruise check deleted a job's records directly before the normal teardown ran, which could leave the job's parent session running and some records orphaned. A correction has been drafted but not applied. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-306",
          "title": "A Cruise test stand-in used a fixed budget instead of the price book",
          "text": "The simulated control plane used in Cruise tests gave every claim a fixed token budget instead of reading the price book figure that the service uses. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-307",
          "title": "An interrupted agent image build could leave an unusable image",
          "text": "If building and publishing an agent image was interrupted, the image or its description file could be left incomplete, and a rebuild reported it as already published without checking, so the engine could not use it. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-308",
          "title": "A lost withdrawal could leave a permission request decidable",
          "text": "When an agent withdrew a permission request and that withdrawal was lost in transit, it was not sent again, so the request stayed open and decidable until its time limit. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-309",
          "title": "The Cruise contract named the wrong stop reason for a refused attempt",
          "text": "The Cruise contract said an attempt stopped for lack of a usable inference key would record one stop reason, while the service records a different one; the contract text was corrected to match and no code changed. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-310",
          "title": "The administration overview could stall on a hanging engine",
          "text": "Loading the service's administration overview asked the engine for its live session count every time, so a hanging engine could hold the page for up to a minute; the count now comes from the regular health probe. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-311",
          "title": "Administration pages showed lists that could not be read as empty",
          "text": "Several administration pages showed a list that could not be read as empty or left it out, and the billing reconciliation view could skip unreadable statements and report no drift. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-312",
          "title": "The public status feed read operational when incidents were unreadable",
          "text": "If the service could not read its incident records, the public status feed reported the service as operational instead of unavailable. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-313",
          "title": "A test scenario stamped its incident in local time marked as UTC",
          "text": "One test scenario recorded the time of the incident it creates in whole seconds and in local time while labelling it as UTC. A correction has been drafted but not applied. The issue remains open.",
          "status": "open",
          "date": "2026-10-01",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: open.",
          "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-314",
          "title": "The website status footer showed a critical incident as paused",
          "text": "When the status feed reported a major outage, the website's status footer had no display for it and showed live measurement as paused instead of an incident in progress. The change had not been merged or deployed at the time of this record. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-315",
          "title": "The administration accounts list showed zero when a read failed",
          "text": "The administration accounts list showed figures that could not be read as zero and silently dropped accounts whose rows could not be read, and its export could be written short. The defect is marked fixed in tests on 1 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-01",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: low. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-316",
          "title": "A cancel during an attempt report was logged as a runner crash",
          "text": "If a customer cancelled a Cruise job while an attempt was still being reported, the job was torn down correctly but the worker recorded a failure and logged a crash. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-317",
          "title": "A cancel just after a Cruise job was claimed was logged as a crash",
          "text": "If a customer cancelled a Cruise job between its claim and the start of its work, the worker recorded a failure and logged a crash instead of a clean teardown. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-318",
          "title": "A stopped Cruise job could still gain new attempt records",
          "text": "The service accepted new attempt records for a Cruise job that had already stopped (in review, accepted, failed or cancelled), so a worker still running after a cancel could add rows to a stopped job's record. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-319",
          "title": "Resumed sessions could stop answering shortly after a resume",
          "text": "A session that answered after being resumed from a checkpoint could stop responding 10 to 60 seconds later and never recover, so a resumed session could be silently lost; the cause was identified in the engine and a fix made there. The defect is marked fixed in tests on 6 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: high. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-320",
          "title": "A test stand-in made one engine test fail intermittently",
          "text": "A stand-in program used by one engine test never read its input, so the test failed intermittently with a broken pipe and turned one build red; the product was not affected. The defect is marked fixed in tests on 12 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-12",
          "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-321",
          "title": "A resume whose session died could hold the engine for about 20 minutes",
          "text": "If a session's virtual machine died or stalled during a resume's clock step, the resume could take about 20 minutes, blocking every checkpoint, resume, fork and kill on that engine meanwhile, and could then report success for a session that was gone. The defect is marked fixed in tests on 6 October 2026.",
          "status": "fixed-in-test",
          "date": "2026-10-06",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-test.",
          "limitation": "Recorded severity: medium. A test fix does not establish a production fix.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-322",
          "title": "Older sessions could not be erased on their own",
          "text": "Sessions saved before a 6 October 2026 change could not be erased individually, and content from their earlier checkpoints stayed readable for as long as the account's key lived. Existing accounts were re-sealed to remove this. The defect is marked fixed in production on 10 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-10",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: high. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-323",
          "title": "Client app help, confirmations and typed commands behaved wrongly",
          "text": "In the ks client's app, help on a command group did not list its commands, a typed ks command was sent to the agent as an instruction (a paid model call), confirmation steps blamed a flag nobody had typed, and kill printed its plan as raw JSON. The defect is marked fixed in production on 11 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-11",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-324",
          "title": "Deletion plans said erasure was incomplete for every session",
          "text": "A session's deletion plan always reported that erasure would not be complete, even for a session whose deletion erases everything, because it only repeated the general retention statement. The defect is marked fixed in production on 11 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-11",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-325",
          "title": "Console actions relied on a cookie setting alone against forged requests",
          "text": "The console's signed-in actions, including approving a device login, were protected only by the session cookie's same-site setting, so a page on another subdomain of the service's domain could have submitted them for a signed-in customer; every such subdomain belonged to KeepState, so this was defence in depth. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-326",
          "title": "An open Agents page stream delayed restarts and was cut without notice",
          "text": "An open event stream on the console's Agents page held a service restart for the full 30 second shutdown limit and was then cut without an end message, so the page reported a lost connection instead of reconnecting at once. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-327",
          "title": "Asynchronous Agents page operations ran without the signed-in account",
          "text": "An operation that the console's Agents page ran asynchronously lost the signed-in account and was refused as unauthenticated; no page used this path before the new agent flow, so nothing in production reached it. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: medium. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-328",
          "title": "The client accepted agent names that the service then refused",
          "text": "The ks client accepted some agent and session names, such as ones starting with a digit, containing a dot or longer than 48 characters, that the service refuses, so the request failed only after it was sent. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        },
        {
          "id": "finding-329",
          "title": "Session journals showed customers internal provisioning detail",
          "text": "A session's event journal showed its readers internal provisioning detail, such as internal identifiers and engine configuration errors, that the provisioning answer deliberately withheld; nothing crossed between accounts. Journal entries written before the fix are kept as they were. The defect is marked fixed in production on 12 October 2026.",
          "status": "fixed-in-production",
          "date": "2026-10-12",
          "scope": "Dated product finding; current deployment has not been independently verified.",
          "result": "Recorded status: fixed-in-production.",
          "limitation": "Recorded severity: low. The register reports a production fix; this publication did not independently retest it.",
          "workaround": "No verified customer workaround is recorded."
        }
      ]
    }
  ],
  "currentDeployment": "Not independently verified by this historical evidence.",
  "canonical": "/evidence/findings"
}

Download this public summary

This derivative has its own digest. It is not the original transcript or a new test. Historical original records are preserved privately.

Download public JSON →

SHA-256 0dd7c6e5e5ed7cd177d0560183ea624f481c49d7d6d9bfc0615d8db7e7828824