{
  "checker": {
    "claims": [
      {
        "claim": "The demo prints and saves a brief in Markdown and JSON under daybook-demo/state/briefs/.",
        "command": "<guest-path> demo --out /tmp/daybook-claim-demo-checker-13fb9ec5b5c04f27ac7d7a1d9306cade",
        "evidence": "# Daybook \u2014 Monday, October 12, 2026\nCovers 2026-10-09\u20132026-10-11 (UTC). 1 active projects, 1 worked yesterday.\n\n## Check you didn't drop anything\nno brief since Fri 2026-10-09; this covers Fri 2026-10-09\u2013Sun 2026-10-11.\nMissing complete briefs in reminder lookback: 2026-10-08, 2026-10-10, 2026-10-11.\n- [cu-55e1f1fada5a4a0b] **sample-app** \u2014 demo-feature has commits but no collected PR or merge evidence (coverage may be incomplete).; first seen Fri, carried 3 days\n- [cu-6e18e869a08d9f05] **sample-app** \u2014 demo-feature has no upstream configured (publication unknown).; first seen Fri, carried 3 ",
        "expected": "printed daily brief with yesterday project activity",
        "input": "synthetic demo",
        "kind": "claim",
        "outcome": "Real input produced the expected result: # Daybook \u2014 Monday, October 12, 2026",
        "returncode": 0,
        "source": "The brief is printed and saved under `daybook-demo/state/briefs/` as Markdown and\nJSON.",
        "source_checked": true,
        "source_file": "README.md",
        "verdict": "yes"
      }
    ],
    "cycle_checks": [
      {
        "claim": "Scheduled or looping main behavior",
        "command": "",
        "evidence": "README states no web server or scheduler is installed; entry points expose one-shot demo and brief commands.",
        "expected": "identify the product trigger",
        "input": "source inspection",
        "kind": "cycle",
        "outcome": "README states no web server or scheduler is installed; entry points expose one-shot demo and brief commands.",
        "source": "repository entry points",
        "verdict": "yes"
      }
    ],
    "details": {
      "argv": [
        "<guest-path>",
        "demo",
        "--out",
        "/tmp/daybook-replay-out-checker-f7a7784d0d294393aa1a6a6e068b56e1"
      ],
      "kind": "cli",
      "needs_browser": false,
      "needs_credentials": false,
      "returncode": 0,
      "scope": "product operation",
      "stderr": "",
      "stdout": "# Daybook \u2014 Monday, October 12, 2026\nCovers 2026-10-09\u20132026-10-11 (UTC). 1 active projects, 1 worked yesterday.\n\n## Check you didn't drop anything\nno brief since Fri 2026-10-09; this covers Fri 2026-10-09\u2013Sun 2026-10-11.\nMissing complete briefs in reminder lookback: 2026-10-08, 2026-10-10, 2026-10-11.\n- [cu-55e1f1fada5a4a0b] **sample-app** \u2014 demo-feature has commits but no collected PR or merge evidence (coverage may be incomplete).; first seen Fri, carried 3 days\n- [cu-6e18e869a08d9f05] **sample-app** \u2014 demo-feature has no upstream configured (publication unknown).; first seen Fri, carried 3 days\n- [cu-84adc6b9e266aeae] **sample-app** \u2014 Document synthetic parser errors.; first seen Fri, carried 3 days\n- [cu-8f11b1d3cb9a9b57] **sample-app** \u2014 Review optional synthetic telemetry.; first seen Fri, carried 3 days\n- [cu-297068e3da6f830c] **sample-app** \u2014 Revisit your last request: Which synthetic error cases still need documentation?; first seen Sun, carried 1 days\n- [cu-bec23740478256f4] **sample-app** \u2014 Unanswered question or next step: Which synthetic error cases still need documentation?; first seen Sun, carried 1 days\n[excerpt truncated]",
      "working": true
    },
    "evidence_strength": "readme_checked",
    "example_checks": [
      {
        "claim": "Run the documented synthetic demo",
        "command": "<guest-path> demo --out /tmp/daybook-example-demo-checker-b2fd0fabfade44008e0c98d1efba6da8",
        "deferred": false,
        "evidence": "sede stale mirrors. Unordered disagreements between files remain conflicts. Distinct native IDs survive. The previous contributing copy keeps source credit while available. Current collection diagnostics are in cache/sessions/diagnostics.json; snapshot counts remain as of the last content change.\nExtensions: 0 repos found, 0 candidates read, 0 dormant; limits hit: none\nLocal git: 1 repos, 1 worktrees; ahead/behind as of the last fetch\nUnassigned sessions: 0 (none)\nModel: 0 calls, 0 s, 0/0 tokens in/out; deferred: none\nFailures: none\nA missing source is a coverage limit, never proof of no work.",
        "expected": "prints a synthetic daily brief",
        "input": "demo output folder",
        "kind": "example",
        "outcome": "command completed successfully",
        "returncode": 0,
        "source": "README.md#Quickstart",
        "verdict": "yes"
      }
    ],
    "status": "PASS"
  },
  "deviations": [
    "README recommended uv Quickstart, but uv was unavailable. Attempted python3 -m pip install --user uv; pip rejected it as an externally-managed-environment (PEP 668). Used the README's documented pip install . alternative inside a venv.",
    "vault-search was not installed in the guest; rg was also unavailable. Used find and direct file reads instead."
  ],
  "fault_owner": null,
  "main_blocker": null,
  "operation": "Run the documented synthetic daily brief demo",
  "operation_scope": "Python 3.12 Linux VM; local daybook-core install in project virtualenv; no credentials, model, or network required by demo",
  "outcome": "working",
  "plain_failure": null,
  "steps": [
    "Read README Quickstart and confirmed Python 3.12 satisfies Python 3.11+.",
    "Initialized Git metadata and fetched/reset to pinned commit 40e1bd45cf6e8c18a332ad1d14fcad52f8acb91c.",
    "Installed Ubuntu python3-pip and python3-venv with apt.",
    "Created .venv and installed local package with python -m pip install . (README release-check installation command).",
    "Ran documented daybook demo --out with a fresh destination; it printed the synthetic Monday brief and created Markdown/JSON artifacts.",
    "Ran checker validation and replay successfully."
  ],
  "stuck_step": null,
  "suggested_fix": null
}