{
  "schemaVersion": "1.0",
  "executionMode": "native-subagents",
  "results": {
    "guidelines": {
      "site": "https://guide.wagtail.org",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "reviewer": {
        "harness": "Codex native subagent",
        "model": "gpt-6.1-sol",
        "reasoning": "high"
      },
      "rows": [
        {
          "checkId": "distraction",
          "guideline": "2.5",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "probes.json:journeys:0"
          ],
          "rationale": "Across the six declared editor-documentation tasks, initial and emulated states show no overlays, playing media or active animations. Navigation, search and page contents support reading; feedback follows the article. The home and release pages contain static conference promotion, but no observed interruption or forced detour. The executed search-to-guide journey reaches the requested instructions. This is limited to observed states, not every later interaction.",
          "confidence": "medium",
          "nextEvidence": "Observe longer reading sessions and optional controls if expanding beyond this bounded sample."
        },
        {
          "checkId": "choice",
          "guideline": "2.6",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "rationale": "No consent banner, transaction, forced registration or accept/reject gate appears in the six sampled pages; ordinary search, theme, language and feedback controls have direct wording. However, the packet has no screenshots or exercised competing-choice states establishing visual prominence/default parity. It supports no demonstrated deceptive pattern, rather than a complete choice assessment.",
          "confidence": "medium",
          "nextEvidence": "Capture the rendered optional menus and feedback states, then inspect any materially competing choices and defaults."
        },
        {
          "checkId": "comprehension",
          "guideline": "2.7",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "The audience is explicitly editors, moderators and administrators. Home distinguishes tutorials, how-to guides, concepts and reference; Overview explains CMS, the sample site and /admin login. Manage images uses task headings, concrete interface names, alt-text guidance and an explicit warning about replacing shared images. Search lists Manage images first with a relevant description. Versioned release headings separate changes; About explains the guide and contribution routes. This supports the sampled English tasks, not comprehension for every audience or translation.",
          "confidence": "medium",
          "nextEvidence": "User testing with new editors and translated or assistive-technology audiences would expand confidence."
        },
        {
          "checkId": "consistency",
          "guideline": "2.8",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:11",
            "source.json:files:12",
            "source.json:files:14"
          ],
          "rationale": "All six pages repeat the same named documentation sections and search/theme controls; content pages repeat Copy page, language selection, in-page headings and feedback patterns where applicable. Search appropriately has its own query form. Candidate base.html is concretely extended by home_page.html and search.html and includes the shared theme and search components. Runtime consistency is independently observed; this does not prove a documented design system or candidate-source deployment.",
          "confidence": "high",
          "nextEvidence": "Review additional languages, menu-open states and design-system documentation for broader coverage."
        },
        {
          "checkId": "motion",
          "guideline": "2.10",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "No active animations or audio/video are recorded across all seven states of each page, including reduced-motion and cold-dark contexts. No observed moving content therefore needs playback controls for these reading states. Candidate main.js contains staggered search-result activation, but the packet does not establish that later animation in the deployed UI; this pass is confined to observed animation, not all possible motion.",
          "confidence": "medium",
          "nextEvidence": "Exercise live autocomplete and menu transitions with and without reduced motion before extending the judgment."
        },
        {
          "checkId": "notifications",
          "guideline": "2.12",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "All six pages and their recorded states show zero notification requestPermission calls and no alert overlays or playing media. Reading and the executed documentation journey require no notification opt-in. Browser permission was already denied, so this establishes absence of attempted requests in the bounded observation, not notification behavior for all permission states or external subscriptions.",
          "confidence": "medium",
          "nextEvidence": "Use a fresh default-permission context and any opt-in journey if expanding the notification scope."
        },
        {
          "checkId": "documents",
          "guideline": "2.13",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "Print emulation hides the global sidebar on all six pages while retaining reading text and task images; article in-page navigation remains. No download-attributed documents are recorded. About nevertheless links Markdown, llms.txt, llms-full.txt and an agent skill with meaningful labels; those linked alternatives were not retrieved. Emulation does not establish pagination, paper use, file size, accessibility or equivalence of the alternatives.",
          "confidence": "medium",
          "nextEvidence": "Inspect an actual print preview/PDF for representative long articles and retrieve linked alternative documents before judging their optimization or equivalence."
        },
        {
          "checkId": "unused-code",
          "guideline": "3.2",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:11",
            "source.json:files:16",
            "source.json:files:17",
            "source.json:files:18"
          ],
          "rationale": "Every page loads the same approximately 89,577-decoded-byte main script, 43,659-decoded-byte stylesheet and translation catalog. Initial 500 ms coverage contains many unexecuted JavaScript functions, including 182\u2013191 zero-count ranges in main.js depending on page; CSS observations list only used ranges and are not an unused-byte total. Candidate main.js initializes search, feedback, mobile menu, theme, copying and other interactions, several absent from the initial snapshot. Neither coverage nor this undeployed source proves those branches are removable.",
          "confidence": "high",
          "nextEvidence": "Collect execution coverage through search autocomplete, mobile navigation, feedback, copying and language/theme interactions; inspect matched deployed source maps/build output before removing code."
        },
        {
          "checkId": "components",
          "guideline": "3.3",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "probes.json:journeys:0",
            "source.json:files:11",
            "source.json:files:16"
          ],
          "rationale": "The same 26,385-byte gzip main bundle loads on all six initial pages. Candidate base.html includes global scripts and candidate main.js imports multiple interaction modules. Search is used later in the executed journey, but the packet lacks deployed bundle attribution and a tested deferred-activation implementation; it does not establish a particular bandwidth-heavy component that can safely be split.",
          "confidence": "medium",
          "nextEvidence": "Attribute deployed bundle modules and compare a deferred component prototype through search/menu activation, caching and slow-network use."
        },
        {
          "checkId": "layout",
          "guideline": "3.10",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "probes.json:journeys:0",
            "source.json:files:17"
          ],
          "rationale": "Desktop 1280 px and resized 360 px states have no horizontal overflow on any sampled page; task text, headings and image counts are retained, with images scaling to 320 px. The sidebar becomes hidden and a named Mobile menu toggle becomes visible. The only executed search journey is desktop; no narrow menu or search control was activated. Candidate menu logic is not deployment proof, so the affected responsive navigation remains unresolved rather than demonstrated broken.",
          "confidence": "high",
          "nextEvidence": "At 360 px, open and close the menu/search, follow a section link and complete the same image-guide task with keyboard and touch emulation. Then sample a real device."
        },
        {
          "checkId": "impact-choice",
          "guideline": "5.4",
          "outcome": "inapplicable",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "The declared scope is reading and finding public documentation. No in-service purchase, transport, media-quality, compute-intensive operation or other materially consequential environmental choice is demonstrated. Theme, search, feedback and links to text alternatives do not alone justify carbon labels. Advice about uploading images describes another CMS workflow rather than an executed upload choice on this service.",
          "confidence": "medium",
          "nextEvidence": "Reassess if auditing actual CMS uploads, media playback or other resource-intensive choices."
        },
        {
          "checkId": "journeys",
          "guideline": "2.4",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:journeys:0",
            "probes.json:pages:2",
            "probes.json:pages:3"
          ],
          "rationale": "The recorded journey clicks homepage search, enters images, submits and opens the Manage images result, with all four actions completed and no errors. The final URL/title/primary heading identify the intended guide, and the final article text explains the Images interface, bulk operations, alt text, focal area and file requirements. The separate results sample also places the relevant guide first. This confirms the declared discovery task, not human usability, optimal step count or every sampled task.",
          "confidence": "high",
          "nextEvidence": "Repeat with representative new editors, narrow-screen controls and less direct search terms to evaluate efficiency more broadly."
        },
        {
          "checkId": "media-delivery",
          "guideline": "2.9",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5",
            "source.json:files:19"
          ],
          "rationale": "The 11 sampled task images occur on Overview (1), Manage images (4) and the 8.1 release (6). Natural widths are 800\u2013900 px versus 756 px desktop and 320 px narrow; none declares srcset/sizes and all use loading=auto. Responses are actually WebP despite .png URLs, with content lengths about 8.8\u201374.4 kB. Screenshots support the instructional content, but legibility at intended pixel densities and alternative renditions were not inspected visually. All article images are fetched initially, including images below the viewport: Manage images totals 233,091 received bytes and the release 354,332, with zero later-byte increase after scroll. These are concrete optimization candidates, not proof a smaller rendition preserves the task.",
          "confidence": "high",
          "nextEvidence": "Visually compare responsive renditions at 1x/2x densities; trial native lazy loading for below-fold instructional screenshots while preserving dimensions and full-detail access. Measure fresh narrow loads and scrolling."
        },
        {
          "checkId": "font-delivery",
          "guideline": "2.11",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "rationale": "All six pages report no document.fonts entries or font network requests. Their body font stack starts with platform/system fonts and includes general sans-serif and emoji fallbacks; visible English content remains present in desktop, narrow and no-JavaScript states. No downloadable web-font loading strategy is needed in this sample, and no font removal or subsetting is warranted.",
          "confidence": "high",
          "nextEvidence": "Sample supported non-Latin languages and constrained devices if expanding typography coverage."
        },
        {
          "checkId": "semantic-forms",
          "guideline": "3.6",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "Each sampled document has lang=en, one main region and one meaningful H1 matching its task. Search inputs have Search label relationships, feedback has Your feedback, and icon controls have explicit names such as Toggle the search form, Mobile menu toggle and Happy/Unhappy. Hidden inputs are not treated as unnamed interactive controls. Search result headings use H4 after H1 and duplicate Search labels are recorded, so this bounded pass does not claim valid heading hierarchy, unique IDs, full accessible names or WCAG compliance.",
          "confidence": "medium",
          "nextEvidence": "Audit the deployed search modal/result heading structure and duplicate search IDs separately, including a screen-reader task."
        },
        {
          "checkId": "metadata",
          "guideline": "3.8",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "The five content pages have descriptive task-specific titles, descriptions and self-referencing HTTPS canonical URLs. Search has a descriptive Search title and robots=noindex; omitting a canonical and description is appropriate for this query result page rather than a missing mandatory field. Each page records one structured-data object that parses as JSON. Parsing does not establish schema correctness or search eligibility; observed declaredType is null and is not silently repaired using undeployed source.",
          "confidence": "high",
          "nextEvidence": "Retrieve and validate deployed structured-data meaning if schema quality becomes an assessment target."
        },
        {
          "checkId": "preference-behavior",
          "guideline": "3.9",
          "outcome": "fail",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "On all six pages desktop light colors are text rgb(38,38,38) on rgb(245,243,248). In live_dark, prefers-color-scheme reports dark=true but these colors and light-theme text remain unchanged. Fresh cold_dark contexts instead render light text on rgb(38,38,38) with task content retained. Thus initial system preference support works but in-page preference change does not meet the declared expectation. No motion is observed in either preference state; no energy saving is inferred from theme color.",
          "confidence": "high",
          "nextEvidence": "Verify a fresh unset user override, then update deployed theme handling for live system changes while preserving an explicit user choice; retest light\u2194dark and persistence."
        },
        {
          "checkId": "no-js-content",
          "guideline": "2.17",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "For each of the six fresh no-JavaScript contexts, the full recorded text, heading observations and navigation observations exactly match desktop. This includes the requested guide instructions and the directly loaded server-rendered search results. Core reading and navigation remain available without scripts; no claim is made that modal search, mobile toggles, copying or every other interaction works without JavaScript.",
          "confidence": "high",
          "nextEvidence": "Execute a no-JavaScript navigation journey and narrow-screen fallback if extending beyond core reading."
        },
        {
          "checkId": "api-requests",
          "guideline": "3.11",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5",
            "probes.json:journeys:0",
            "source.json:files:15",
            "source.json:files:16"
          ],
          "rationale": "Initial network windows contain documents, scripts, styles and images, with no duplicate URL requests or Fetch/XHR polling; scroll adds no requests/bytes in all six staged runs. Candidate main.js uses debounced task-triggered autocomplete rather than a polling loop. However, the journey submits quickly and provides only before/after resource snapshots, not a complete intermediate API trace, so autocomplete requests, stale-result handling and payload necessity cannot be judged from deployed behavior.",
          "confidence": "high",
          "nextEvidence": "Capture typing, pauses, clearing and repeated searches with request/response timings, payloads and cancellation/cache behavior; relate freshness to the documentation task."
        },
        {
          "checkId": "public-cache-policy",
          "guideline": "4.2",
          "outcome": "cantTell",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "rationale": "Hashed public CSS and JS declare max-age=315360000, public, immutable with ETag/Last-Modified. All sampled remote images have ETag and Last-Modified, supporting validation even without explicit Cache-Control. The per-language /en/jsi18n/ script lacks client cache/validation headers on four page responses, while home/search observations include Age and Last-Modified. Its intended freshness and delivery policy are unresolved. Header-only observations also do not prove warm reuse or offline access.",
          "confidence": "medium",
          "nextEvidence": "Check catalog freshness/invalidation requirements and response consistency, then compare a warm repeat visit and navigation with observed request/304/cache reuse."
        },
        {
          "checkId": "text-compression",
          "guideline": "4.3",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "rationale": "Across all six sampled 200 responses, HTML and the translation catalog are delivered with Brotli and the shared CSS/main/blocking scripts with gzip. The main script and stylesheet have compressed content lengths of 26,385 and 8,247 bytes versus observed decoded sizes of 89,577 and 43,659 bytes. This supports beneficial compression of material sampled text assets; already-compressed WebP images and inline data images are not required to carry an additional content encoding.",
          "confidence": "high",
          "nextEvidence": "No further evidence needed for the sampled text-delivery expectation."
        },
        {
          "checkId": "keyboard-path",
          "guideline": "3.6",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "rationale": "All six twelve-Tab traces start with the visible Skip to main content link, named home link and search toggle, then meaningful documentation links including Manage images. Every recorded focused element is visible, focusVisible=true and has a solid 2 px blue outline rgb(49,120,250), a discernible indicator against the sampled light background. This establishes the bounded initial path, not activated skip-link behavior, modal traps, reverse navigation, every control or complete accessibility.",
          "confidence": "high",
          "nextEvidence": "Activate the skip link and modal/menu controls, test reverse traversal and capture visual focus in dark and narrow states for broader keyboard coverage."
        },
        {
          "checkId": "disclosure-scope",
          "guideline": "2.1",
          "outcome": "cantTell",
          "evidenceIds": [
            "staged.json:discovery:0",
            "disclosures.json:sites:0",
            "probes.json:pages:5"
          ],
          "rationale": "Discovery retrieves no usable sustainability statement: the two common-path candidates redirect to localized paths returning 404, and carbon records are empty. About describes purpose/contribution rather than service impacts and mitigation. This bounded search does not establish that no public policy exists elsewhere or that a wider Wagtail policy covers this origin.",
          "confidence": "high",
          "nextEvidence": "Request the service-specific public statement or an explicit scoped relationship to a parent policy, then read its impacts, mitigation and review date."
        },
        {
          "checkId": "carbon-discovery",
          "guideline": "3.13",
          "outcome": "fail",
          "evidenceIds": [
            "staged.json:discovery:0",
            "disclosures.json:sites:0"
          ],
          "rationale": "Root /carbon.txt and /.well-known/carbon.txt return 404 HTML with no redirects or Carbon-Location; discovery records no DNS/header delegation or usable carbon records. The sampled v0.x discovery profile therefore does not expose a parseable carbon.txt relationship. This is only the declared optional-file check, not proof of high emissions, absent sustainability work or failure of all WSG 3.13.",
          "confidence": "high",
          "nextEvidence": "If beneficial for transparency, publish a valid carbon.txt or supported delegation with service/provider relationships and independently inspect the linked evidence; reassess using the declared profile."
        },
        {
          "checkId": "hosting-evidence",
          "guideline": "4.1",
          "outcome": "cantTell",
          "evidenceIds": [
            "disclosures.json:sites:0",
            "staged.json:discovery:0",
            "source.json:files:4"
          ],
          "rationale": "No retrieved hosting sustainability evidence or carbon record identifies an independently corroborated operational scope for this origin. Candidate Dockerfile comments describe Heroku production, but this owner-supplied source has deploymentVerified=false and does not establish provider/account/region, energy mix, operational metrics or sustainable hosting. No green-hosting flag is justified.",
          "confidence": "high",
          "nextEvidence": "Obtain origin-to-provider/region deployment evidence plus current provider operational disclosures or independently verified hosting evidence."
        },
        {
          "checkId": "source-reuse",
          "guideline": "3.4",
          "outcome": "pass",
          "evidenceIds": [
            "source.json:files:11",
            "source.json:files:12",
            "source.json:files:13",
            "source.json:files:14",
            "source.json:files:16",
            "source.json:files:17"
          ],
          "rationale": "In clean candidate revision 31a4547eb1f6de55baea84269723313784f6b544, base.html lines 99\u2013132 includes shared skip/theme/copy/search components; home_page.html line 1 and search.html line 1 concretely extend that base. main.js uses component initialization for MobileMenu/CopyButton. The modal and full-page search forms serve different contexts, so similar fields alone do not prove a harmful duplicate maintenance path. This passes selected-source reuse only; deploymentVerified=false and unselected modules remain outside scope.",
          "confidence": "high",
          "nextEvidence": "Inspect more concrete component call sites only if extending the source scope."
        },
        {
          "checkId": "source-dependencies",
          "guideline": "3.12",
          "outcome": "cantTell",
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:2",
            "source.json:files:3",
            "source.json:files:4",
            "source.json:files:7"
          ],
          "rationale": "The clean candidate revision lists direct Python and npm dependencies in pyproject.toml and package.json. Dockerfile/CI explicitly use npm ci and uv sync --frozen, demonstrating an intended repeatable resolution mechanism. However, uv.lock and package-lock.json are metadata_only: their validity, consistency and resolved contents are not exposed. Thus the complete repeatability expectation cannot pass from filenames alone. Installed/deployed versions, necessity, vulnerabilities and freshness are not established; deploymentVerified=false.",
          "confidence": "high",
          "nextEvidence": "Capture bounded lockfile root/manifest-resolution evidence or a clean frozen install receipt at the same revision, then separately verify deployed inventory if needed."
        },
        {
          "checkId": "source-runtime",
          "guideline": "3.15",
          "outcome": "pass",
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:4",
            "source.json:files:5",
            "source.json:files:6",
            "source.json:files:7",
            "source.json:files:8"
          ],
          "rationale": "At clean candidate revision 31a4547eb1f6de55baea84269723313784f6b544, pyproject requires Python >=3.14, .python-version declares 3.14 and Dockerfile uses python:3.14; README requests 3.14 or higher. .nvmrc declares 26, Dockerfile frontend uses node:26 and CI setup-node reads .nvmrc. These selected declarations are mutually consistent for the documented path. Dockerfile.dev is unselected, deploymentVerified=false, and no authoritative release reference supports a latest-stable or deployed-version claim.",
          "confidence": "high",
          "nextEvidence": "Capture Dockerfile.dev and deployed runtime attestations if expanding beyond selected declaration consistency."
        },
        {
          "checkId": "source-automation",
          "guideline": "4.6",
          "outcome": "fail",
          "evidenceIds": [
            "source.json:files:7"
          ],
          "rationale": "In clean candidate revision 31a4547eb1f6de55baea84269723313784f6b544, ci.yml lines 3\u20138 runs on pushes to main and renovate/** as well as every pull_request. For a renovate branch with an open PR, the same update matches both events and runs both docker-build-check and test workflows. The 55-line selected workflow has no event exclusion, concurrency/cancel-in-progress or other equivalent control. This demonstrates a duplicate-trigger path in candidate automation; execution history/energy and its current repository deployment are not established. Necessary validation jobs should be retained.",
          "confidence": "medium",
          "nextEvidence": "Verify an open Renovate PR run pair and required checks, then deduplicate matching event contexts or cancel superseded runs without losing branch validation."
        },
        {
          "checkId": "source-maintenance",
          "guideline": "5.10",
          "outcome": "pass",
          "evidenceIds": [
            "source.json:files:8",
            "source.json:files:9",
            "source.json:files:7"
          ],
          "rationale": "In the clean candidate revision, README lines 23\u2013103 documents dependencies, local/container setup and development commands; lines 105\u2013114 identify contribution, lint and test commands. CONTRIBUTING explains content/translation coordination, permissions, release copying and screenshot refresh. CI concretely invokes lint/tests. This passes documentation disclosure for selected candidate source, not proof of staffing, regular execution or a complete sustainability/security strategy; deploymentVerified=false.",
          "confidence": "high",
          "nextEvidence": "Owner maintenance cadence, staffing and operational records would support the broader guideline."
        },
        {
          "checkId": "source-change-docs",
          "guideline": "5.12",
          "outcome": "pass",
          "evidenceIds": [
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:9"
          ],
          "rationale": "The live New in Wagtail 8.1 page gives identifiable versioned user-facing changes, practical effects and a link to full technical release notes; navigation lists earlier releases and the page is dated November 3, 2026. About links historical copies in the guide repository. Candidate CONTRIBUTING lines 37\u201365 explains matching latest documentation and screenshot copies to releases. Thus useful change documentation is actually visible; candidate deploymentVerified=false does not erase this independent runtime evidence, while receipt by every affected user is not proven.",
          "confidence": "high",
          "nextEvidence": "Review translated and older release guidance when expanding change-history coverage."
        },
        {
          "checkId": "source-budgets",
          "guideline": "5.24",
          "outcome": "cantTell",
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:4",
            "source.json:files:7",
            "source.json:files:8",
            "source.json:files:9"
          ],
          "rationale": "None of the selected captured manifests, Dockerfile, CI workflow or contributor documentation defines a concrete asset/performance limit plus an exceedance response. The package build script and linters alone do not establish a relevant budget. Build configuration such as vite.config.ts is referenced but not captured; therefore this is a bounded search gap, not proof the project or organization lacks budgets. Candidate deploymentVerified=false.",
          "confidence": "high",
          "nextEvidence": "Capture build-budget configuration and its failing/warning threshold, enforcement behavior and owner-approved rationale, or obtain the relevant project budget document."
        },
        {
          "checkId": "source-open-source",
          "guideline": "5.25",
          "outcome": "pass",
          "evidenceIds": [
            "source.json:files:8",
            "source.json:files:9",
            "source.json:files:10",
            "probes.json:pages:5"
          ],
          "rationale": "The selected clean candidate LICENSE gives source/binary redistribution terms with conditions, while README/CONTRIBUTING explain code, documentation, issue and translation participation routes. Separately the live site footer declares CC0 for content, and About links its historical repository and contribution/issues routes. This supports scoped reuse terms and ways to contribute; it does not prove ongoing upstream contributions, and candidate code deployment is unverified.",
          "confidence": "high",
          "nextEvidence": "No further evidence needed for these selected reuse/contribution disclosures; verify upstream activity only for a broader claim."
        }
      ],
      "topFindings": [
        {
          "checkId": "preference-behavior",
          "priority": "medium",
          "title": "Follow live system theme changes",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "summary": "Fresh dark loads work, but all six already-open pages retain light colors after the system preference changes.",
          "recommendedAction": "Update theme preference handling while preserving explicit user overrides, then test light-to-dark and dark-to-light changes without reloading.",
          "status": "observed defect"
        },
        {
          "checkId": "media-delivery",
          "priority": "medium",
          "title": "Trial deferred screenshot loading and responsive renditions",
          "evidenceIds": [
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:4",
            "staged.json:runs:2",
            "staged.json:runs:4"
          ],
          "summary": "Instructional images are eagerly fetched at 800\u2013900 px even when rendered at 320 px. The image-guide and release pages receive about 233 kB and 354 kB initially, with no extra bytes after scroll. WebP delivery already works.",
          "recommendedAction": "Trial native lazy loading below the first viewport and compare responsive variants at intended densities, preserving screenshot text legibility and full-detail access before claiming savings.",
          "status": "investigation"
        },
        {
          "checkId": "source-automation",
          "priority": "medium",
          "title": "Deduplicate the Renovate push and PR validation path",
          "evidenceIds": [
            "source.json:files:7"
          ],
          "summary": "The selected candidate workflow triggers on renovate/** pushes and all pull requests with no equivalent deduplication or superseded-run cancellation. An open Renovate PR update matches both.",
          "recommendedAction": "Confirm the run pair and required-check names, then filter duplicate events or cancel superseded runs while retaining necessary build and test coverage.",
          "status": "candidate source defect; deployment unverified"
        },
        {
          "checkId": "layout",
          "priority": "low",
          "title": "Verify the mobile navigation task before accepting responsive support",
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "probes.json:journeys:0"
          ],
          "summary": "All six pages fit 360 px without horizontal overflow, but the sidebar is hidden and the replacement mobile menu was not activated. The recorded search journey is desktop only.",
          "recommendedAction": "At 360 px, open and close navigation/search and complete the image-guide task, including keyboard traversal and a representative real device.",
          "status": "evidence gap"
        }
      ]
    },
    "evidence": {
      "role": "evidence",
      "site": "https://guide.wagtail.org",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "reviewer": {
        "harness": "Codex native subagent",
        "model": "gpt-6.1-sol",
        "reasoning": "high"
      },
      "issues": [
        {
          "id": "evidence-01-phase-and-accounting",
          "checkIds": [
            "choice",
            "media-delivery",
            "impact-choice"
          ],
          "evidenceIds": [
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "summary": "All six initial captures have complete_within_protocol accounting, no unresolved requests, no coverage gaps and no resource errors. Initial bytes are 59103, 63630, 233091, 50608, 354332 and 54159. Both subsequent cumulative checkpoints equal their initial total. Every branch is no_banner and actions is empty: after_consent names a checkpoint but no consent decision occurred.",
          "requestedChange": "Use initial as the headline; label the other checkpoints as cumulative after a no-action consent checkpoint and after scrolling, each adding 0 bytes. Do not report consent savings, independent page-load totals, missing resources, or a measured full-site average. Preserve the bounded main-CDP, 3-second, DPR-1 protocol and separate the byte-based SWDM scenario from direct energy or WSG scoring."
        },
        {
          "id": "evidence-02-eager-article-images",
          "checkIds": [
            "media-delivery",
            "components"
          ],
          "evidenceIds": [
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:4",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:4"
          ],
          "summary": "The overview image (9600 bytes), four manage-images screenshots (177373 bytes, 76.1% of 233091-byte initial load) and six release-note images (297681 bytes, 84.0% of 354332-byte initial load) all finish in initial. All have loading=auto, no srcset, and desktop top positions below the 800px initial viewport: overview y=1403.9; manage-images y=878.4 to 3245.4; release notes y=1024.8 to 5049.2. Scrolling adds no image requests or bytes.",
          "requestedChange": "Prioritize testing deferral of farther-below-fold article screenshots, with preserved dimensions and successful loading during reading, print and no-JavaScript behavior. Describe these totals as traffic present on the initial load, not measured avoidable savings; native lazy-loading thresholds may still fetch near-fold images. Do not claim that deferral or its activation has already been tested."
        },
        {
          "id": "evidence-03-negotiated-image-format",
          "checkIds": [
            "media-delivery",
            "text-compression"
          ],
          "evidenceIds": [
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:4"
          ],
          "summary": "Every measured external article image is served with image/webp MIME type and Vary: accept, accept-encoding even though the URL ends in .png. ETags are present. The URL extension is not the delivered encoding.",
          "requestedChange": "Credit observed negotiated WebP delivery. Do not recommend converting these responses from PNG to WebP or adding HTTP compression to already-compressed images. Further format/quality comparisons require captured alternatives and legibility checks."
        },
        {
          "id": "evidence-04-rendition-legibility-density",
          "checkIds": [
            "media-delivery",
            "layout"
          ],
          "evidenceIds": [
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:4",
            "source.json:files:19"
          ],
          "summary": "The article screenshots render at 756 CSS px on desktop and 320 CSS px after resizing to 360px. Natural widths are 900px except three release-note images at 800px, all at DPR 1. The frozen packet has dimensions and alt text but no screenshot pixels or tested alternative renditions; these are instructional screenshots containing interface details. Narrow is the same document resized, not a new mobile cold load.",
          "requestedChange": "Treat responsive renditions as an investigation candidate, not a demonstrated sizing failure or quantified saving. Check readability and useful detail at intended DPRs before prescribing 320px or 756px variants. Do not infer a new narrow-load transfer result. The selected SCSS describes presentation only and does not establish the deployed rendition generator or an exact template fix."
        },
        {
          "id": "evidence-05-live-versus-cold-theme",
          "checkIds": [
            "preference-behavior"
          ],
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:18"
          ],
          "summary": "All six desktop pages start light. In every live_dark state, preferences.dark=true while body foreground/background remain rgb(38,38,38)/rgb(245,243,248). Every fresh cold_dark state uses the inverse colors and preserves the same task content, with only the theme control text changing from Dark mode to Light mode. The selected source file wires a click event but does not contain the underlying theme initialization/change listener.",
          "requestedChange": "Report the reproducible distinction: cold dark preference is honored; an in-page system dark preference change is not reflected in the observed colors. Investigate the actual theme listener and explicit-user-choice policy before naming a source fix. Do not claim dark mode is wholly unsupported, that the unactivated manual toggle fails, or that this proves measured energy savings."
        },
        {
          "id": "evidence-06-code-coverage-interpretation",
          "checkIds": [
            "unused-code",
            "components"
          ],
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:16"
          ],
          "summary": "Coverage is initial load plus 500ms and main target only. Main script source extends to offset 89576 while its compressed body is 26385 bytes; execution offsets and network bytes use different units. Zero-count JavaScript ranges occur before search/menu/copy/feedback activation. All recorded cssRuleUsage entries have used=true; the packet does not include an inventory of every stylesheet rule or total unused CSS.",
          "requestedChange": "Use coverage to nominate representative interaction/source investigations only. Do not publish a removable-code byte saving, equate source offsets with transferred bytes, sum overlapping function ranges, or interpret all recorded CSS rules being used as 0% unused CSS. The candidate source shows later interaction features in the main bundle but does not establish a safely deferred split or deployed module identity."
        },
        {
          "id": "evidence-07-cache-and-compression-boundaries",
          "checkIds": [
            "public-cache-policy",
            "text-compression"
          ],
          "evidenceIds": [
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "summary": "All measured HTML and jsi18n script responses are Brotli-compressed; hashed static CSS and JavaScript are gzip-compressed and expose max-age=315360000, public, immutable plus ETag. Image responses expose ETag but no cache-control in the allowlisted headers. HTML/jsi18n likewise have no captured explicit cache policy. The sample contains no private no-store responses and no warm-load experiment.",
          "requestedChange": "Distinguish the strong explicit policy on versioned static assets from validation-only observed image headers and unknown reuse for dynamic documents/catalogs. Header absence does not prove no caching, and immutable/ETag do not prove measured warm reuse or offline support. Do not characterize the site as uncompressed or uncached; scope any caching follow-up to public images/catalog policy and a real repeat-load test."
        },
        {
          "id": "evidence-08-resource-timing-zeros",
          "checkIds": [
            "media-delivery",
            "api-requests",
            "public-cache-policy"
          ],
          "evidenceIds": [
            "staged.json:runs:2",
            "staged.json:runs:4",
            "probes.json:pages:2",
            "probes.json:pages:4",
            "probes.json:journeys:0"
          ],
          "summary": "Cross-origin article-image Resource Timing entries report transferSize/encodedBodySize/decodedBodySize of zero, including after the successful journey, while staged CDP accounting measures 177373 and 297681 image bytes. The journey also has zero transferSize for some same-origin static assets in its reused context. Supplemental resource timing is explicitly not headline transfer accounting.",
          "requestedChange": "Use staged CDP receivedBytes for traffic and carbon inputs. Treat zero cross-origin Resource Timing sizes as restricted/unavailable evidence, not zero-byte images. Do not total journey Resource Timing as a measured journey footprint or use those zeros alone to prove caching effectiveness."
        },
        {
          "id": "evidence-09-journey-completion-scope",
          "checkIds": [
            "journeys",
            "api-requests",
            "choice",
            "layout"
          ],
          "evidenceIds": [
            "probes.json:journeys:0",
            "probes.json:pages:3",
            "source.json:files:16"
          ],
          "summary": "The declared journey completes four actions: open search, fill images, press Enter, click the Manage images result. All actions succeed, actual URL equals the target, one h1 matches Manage images, and status is satisfied. The legacy successSelectorVisible field is null but the explicit completion conditions are all true. Fill and Enter occur about 27ms apart, so this does not exercise a deliberate wait for autocomplete. Before/after snapshots do not provide a complete intermediate journey network log.",
          "requestedChange": "Credit the completed bounded search-to-guide journey. Do not infer failure from the null legacy field or claim optimal usability, search pagination, autocomplete request efficiency, mobile-menu activation, feedback, clipboard behavior, or all keyboard paths were tested. Initial networks show no Fetch/XHR polling in their bounded windows; they do not establish absence during autocomplete or later use."
        },
        {
          "id": "evidence-10-probe-scope-and-positive-behavior",
          "checkIds": [
            "layout",
            "no-js-content",
            "font-delivery",
            "motion",
            "notifications",
            "keyboard-path",
            "documents"
          ],
          "evidenceIds": [
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:3",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "summary": "All desktop and narrow states have no horizontal overflow and retain one visible h1/main. Fresh no-JavaScript body text equals desktop body text on every page. No document.fonts entries or font network responses occur; body uses a system fallback stack. All observed animation lists are empty and permission-request call count is zero. Twelve desktop Tab steps consistently show visible focus with a solid 2px outline. Print emulation hides global navigation while retaining article images/content, but no PDF pagination or downloaded document was inspected.",
          "requestedChange": "Preserve these scoped strengths without inventing web-font reductions or missing-content defects. Narrow navigation is hidden behind an unactivated menu, so its functionality remains unknown. Empty motion/notification lists and bounded Tab steps do not establish all-time behavior or full accessibility. No-JavaScript reading availability does not prove no-JavaScript search or other controls. Print emulation does not prove optimized PDF output, pagination, or document accessibility."
        },
        {
          "id": "evidence-11-search-metadata-applicability",
          "checkIds": [
            "metadata"
          ],
          "evidenceIds": [
            "probes.json:pages:3",
            "probes.json:pages:0",
            "probes.json:pages:1",
            "probes.json:pages:2",
            "probes.json:pages:4",
            "probes.json:pages:5",
            "source.json:files:11"
          ],
          "summary": "Five content pages have descriptive titles, descriptions and canonical URLs. Search intentionally declares robots=noindex and lacks canonical/description. Every sampled structured-data block parses as JSON, but the probe records declaredType=null, while candidate base.html uses @type=WebPage. The packet does not contain a schema-validation result for deployed JSON-LD.",
          "requestedChange": "Assess search metadata according to its internal, noindex purpose rather than a mandatory-description/canonical checklist. Do not treat declaredType=null as evidence that deployed JSON-LD lacks @type, nor equate JSON parsing with schema validity or search eligibility. If typed structured data matters to the conclusion, request deployed block content or a parser check through the coordinator."
        },
        {
          "id": "evidence-12-source-and-technology-attribution",
          "checkIds": [
            "source-reuse",
            "source-dependencies",
            "source-runtime",
            "source-automation",
            "source-maintenance",
            "source-change-docs",
            "source-budgets",
            "source-open-source",
            "hosting-evidence"
          ],
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:2",
            "source.json:files:3",
            "source.json:files:7",
            "source.json:files:8",
            "source.json:files:11",
            "staged.json:runs:0"
          ],
          "summary": "Selected source is owner-supplied candidate source at clean tracked revision 31a4547eb1f6de55baea84269723313784f6b544 with deploymentVerified=false. Both lockfiles are metadata_only, not captured dependency listings. Wappalyzer at staged.json /technology heuristically detects Wagtail, Python, Django, Cloudflare and Open Graph with empty versions in a separate scan; those requests are excluded from staged totals. That top-level technology object has no dedicated evidenceIndex entry.",
          "requestedChange": "Retain deployment uncertainty on every claimed fix location and separate declared dependencies/runtime from installed or deployed versions. A selected-files search cannot prove organizational absence of budgets or maintenance practice. Cite Wappalyzer as heuristic context, not backend-cost measurement or a verified technology version. Cloudflare is CDN evidence, not proof of origin provider or green electricity; do not set a green SWDM flag from it. Preserve the missing dedicated technology evidence pointer if formal downstream citation requires one, rather than inventing an ID."
        }
      ]
    },
    "claims": {
      "role": "claims",
      "site": "https://guide.wagtail.org",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "reviewer": {
        "harness": "Codex native subagent",
        "model": "gpt-6.1-sol",
        "reasoning": "high"
      },
      "issues": [
        {
          "id": "guide-discovery-scope",
          "checkIds": [
            "carbon-discovery",
            "disclosure-scope"
          ],
          "evidenceIds": [
            "staged.json:discovery:0",
            "disclosures.json:sites:0"
          ],
          "summary": "Root and well-known carbon.txt returned 404, and the two common sustainability-document paths redirected to localized 404s. No file was retrieved, so TOML, schema, declared version, delegation and provider/document relationships cannot be assessed. The bounded DNS/header/path discovery does not establish that no policy exists elsewhere.",
          "requestedChange": "Report carbon.txt as not found within this discovery scope and sustainability disclosure as unresolved. Ask the owner for an origin-specific statement and any discovery/delegation route; verify its final document, dates and explicit guide.wagtail.org scope before crediting a parent-domain policy. Do not turn these 404s into a high-emissions claim."
        },
        {
          "id": "guide-hosting-unknown",
          "checkIds": [
            "hosting-evidence"
          ],
          "evidenceIds": [
            "staged.json:discovery:0",
            "source.json:files:4",
            "staged.json:runs:0"
          ],
          "summary": "No substantiating hosting disclosure was retrieved. The candidate Dockerfile describes Heroku production, but deployment identity is unknown. A CDN/fingerprint or candidate deployment comment does not establish origin region, electricity supply or sustainable operations. The SWDM run explicitly assumes non-green hosting for its scenario.",
          "requestedChange": "Keep sustainable hosting unresolved and keep the model assumption labeled as an assumption. Obtain an origin-to-provider/service/region relationship and dated independent operational evidence before making a green-hosting claim or changing the SWDM flag; distinguish CDN delivery from origin hosting."
        },
        {
          "id": "guide-model-boundary",
          "checkIds": [
            "disclosure-scope",
            "impact-choice"
          ],
          "evidenceIds": [
            "staged.json:runs:0",
            "staged.json:runs:1",
            "staged.json:runs:2",
            "staged.json:runs:3",
            "staged.json:runs:4",
            "staged.json:runs:5"
          ],
          "summary": "The runs contain provisional SWDM v4 estimates for sampled cold page loads using CDP bytes, 100% first visits, 0% return visits and unknown hosting treated as non-green. These are model outputs, including operational and embodied browsing boundaries, rather than measured energy, an organizational inventory, or a validated public badge. No matched-origin annual traffic evidence is in this packet.",
          "requestedChange": "Retain library/version, phase, byte definition, incomplete observation boundaries and first/repeat assumptions alongside any per-page figures. Do not claim measured annual emissions or a DCR badge. An annual scenario needs matched-origin traffic with its period/calibration and an explicit page mix; average repeated branches within each page before page weighting and convert grams to kilograms once. Keep any browser CPU energy separate from SWDM."
        },
        {
          "id": "guide-source-identity",
          "checkIds": [
            "source-reuse",
            "source-dependencies",
            "source-runtime",
            "source-automation",
            "source-maintenance",
            "source-change-docs",
            "source-budgets",
            "source-open-source"
          ],
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:2",
            "source.json:files:3",
            "source.json:files:4",
            "source.json:files:5",
            "source.json:files:6",
            "source.json:files:7",
            "source.json:files:8",
            "source.json:files:9",
            "source.json:files:10",
            "source.json:files:11",
            "source.json:files:12",
            "source.json:files:13",
            "source.json:files:14",
            "source.json:files:15",
            "source.json:files:16",
            "source.json:files:17",
            "source.json:files:18",
            "source.json:files:19"
          ],
          "summary": "All 20 selected source records describe local/guide revision 31a4547eb1f6de55baea84269723313784f6b544 with a clean tracked working tree; deploymentVerified is false. Two lockfiles are metadata-only. This is a selected candidate-source snapshot, not an installed-package, full-project, vulnerability or deployed-runtime inventory.",
          "requestedChange": "Attach the revision and deployment uncertainty to source findings. Use these files as plausible edit locations and validate a proposed change in the actual deployed path before promising visitor savings. Do not infer project-wide missing practices or installed/deployed versions from the selection, clean tracked status or source comments."
        },
        {
          "id": "guide-lock-validation",
          "checkIds": [
            "source-dependencies"
          ],
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:1",
            "source.json:files:2",
            "source.json:files:3",
            "source.json:files:4",
            "source.json:files:7"
          ],
          "summary": "Manifests declare dependencies, Docker and CI use npm ci and uv sync --frozen, but uv.lock and package-lock.json expose identity/size only. Their presence and installer commands support a repeatable-resolution mechanism, but do not verify the contents, manifest compatibility, package necessity, security or deployed versions.",
          "requestedChange": "Credit the declared mechanism at its actual scope; inspect captured lockfile contents or obtain a successful frozen build receipt if lock validity matters to the judgment. Establish component/task use before removing Bootstrap/Popper, and obtain an authoritative captured advisory/release reference before claiming dependencies are vulnerable or outdated."
        },
        {
          "id": "guide-runtime-and-ci-scope",
          "checkIds": [
            "source-runtime",
            "source-automation"
          ],
          "evidenceIds": [
            "source.json:files:0",
            "source.json:files:4",
            "source.json:files:5",
            "source.json:files:6",
            "source.json:files:7",
            "source.json:files:8"
          ],
          "summary": "Selected runtime declarations align at Python 3.14 and Node 26, while README allows Python 3.14 or higher. This supports declaration consistency only. CI pushes to main/renovate branches and pull requests, with build checks plus lint/tests; it declares no concurrency cancellation. A renovate PR can plausibly overlap, but no run history demonstrates duplicate work or measured CI energy.",
          "requestedChange": "Do not claim latest-stable or deployed versions without authoritative release and deployment evidence. Review actual overlapping renovate/PR and superseded runs before recommending event filtering or concurrency cancellation; preserve required build/lint/test coverage and measure the effect rather than claiming automatic energy savings."
        },
        {
          "id": "guide-maintenance-change-license",
          "checkIds": [
            "source-maintenance",
            "source-change-docs",
            "source-open-source"
          ],
          "evidenceIds": [
            "source.json:files:8",
            "source.json:files:9",
            "source.json:files:10",
            "probes.json:pages:4",
            "probes.json:pages:5"
          ],
          "summary": "README and CONTRIBUTING document setup, checks, CMS content contribution, translation and version-copy procedures; LICENSE supplies BSD source-code terms. The sampled public release page explains Wagtail 8.1 changes, the About page describes historical copies, and the public footer separately states CC0. These are positive disclosures, but do not prove routine execution, staffing, deployment-linked site change logs or ongoing upstream contributions.",
          "requestedChange": "Preserve the distinction between Wagtail product release notes, guide-site changes, source licensing and public content licensing. Credit the documented maintenance/contribution paths without inferring execution. If site-change communication is needed, request the owner\u2019s actual channel rather than calling it absent because a changelog was not selected."
        },
        {
          "id": "guide-budget-selection-limit",
          "checkIds": [
            "source-budgets"
          ],
          "evidenceIds": [
            "source.json:files:1",
            "source.json:files:7",
            "source.json:files:8",
            "source.json:files:9"
          ],
          "summary": "The selected scripts, CI and project documents show validation commands but no explicit asset/performance limit with an exceedance response. Build configuration was not selected, so an organization-wide absence of budgets is unsupported.",
          "requestedChange": "Keep the selected-source budget judgment unresolved and request relevant build/budget policy or CI evidence. If none exists, agree a representative reading/search and image-documentation budget with maintainers and specify warning/failure ownership before adding enforcement."
        },
        {
          "id": "guide-ui-edit-prerequisites",
          "checkIds": [
            "source-reuse",
            "unused-code",
            "components",
            "api-requests",
            "semantic-forms"
          ],
          "evidenceIds": [
            "source.json:files:11",
            "source.json:files:12",
            "source.json:files:13",
            "source.json:files:14",
            "source.json:files:15",
            "source.json:files:16",
            "source.json:files:17",
            "probes.json:journeys:0"
          ],
          "summary": "The base shares header/footer and a search modal; full-page search is a distinct GET fallback. Both search templates use id=search, so the inherited search page is a concrete candidate for duplicate-ID inspection. main.js debounces autocomplete by 150ms and stages result animation by 400ms per result; the journey submits with Enter and does not exercise incremental autocomplete races or prove safe removal of the component bundle.",
          "requestedChange": "Check deployed search-page label/ID relationships before proposing unique IDs, and exercise autocomplete typing, result order, keyboard use and fallback submission before changes. If stale requests or needless animations are confirmed, target main.js with cancellation/order guards or proportionate rendering, and validate task completion and requests. Do not consolidate modal/full-page search, remove dependencies or defer the bundle solely from initial code coverage."
        },
        {
          "id": "guide-preferences-and-images-prerequisites",
          "checkIds": [
            "preference-behavior",
            "media-delivery",
            "font-delivery",
            "motion"
          ],
          "evidenceIds": [
            "source.json:files:11",
            "source.json:files:16",
            "source.json:files:18",
            "source.json:files:19",
            "probes.json:pages:2"
          ],
          "summary": "theme-detect/index.js only dispatches a toggle event while base.html loads blocking.js; the selected excerpt is not the complete theme implementation. rich-text-image.scss sets full-width images to width:100% with auto height, but does not expose CMS rendition generation. The guide explicitly documents multilingual/RTL requirements and image screenshots serve instructional tasks.",
          "requestedChange": "Preserve working theme behavior unless cold and in-page preference observations show a defect; request the blocking script before a source fix. Check actual rendition call sites, delivered dimensions, legibility at target pixel densities and narrow layouts before replacing screenshots or promising image savings. Establish language/fallback needs before font subsetting or removal. Missing selected implementation is not absent functionality."
        }
      ]
    }
  },
  "acceptanceReceipts": {
    "guidelines": {
      "role": "guidelines",
      "taskSHA256": "9cc580bcc5fd94ed6791c4e2077085e70fac2a9f94f66cc857878ee4c8bf9a38",
      "resultSHA256": "81b9b340955150748c990d2b225405e1d50a48e1d75ce91d26e73137bd511bcd",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "executionMode": "native-subagents"
    },
    "evidence": {
      "role": "evidence",
      "taskSHA256": "3f3e0ddd83aef6e623977b47f5b27949126d75e0f96cfb4a7606c517c729ec38",
      "resultSHA256": "db666c6a0d015e970248b7a4d6b782912e57e2dc8706effd63d2c0cbc15c5ffe",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "executionMode": "native-subagents"
    },
    "claims": {
      "role": "claims",
      "taskSHA256": "3564a49602dcbd396aa75ee9516f85afff382361280840db0331ec47eef14f0d",
      "resultSHA256": "3e4f27c6b6e0fde8495689013dc2cb643ccfc821d76b8447b8f1ce17074da511",
      "packetSHA256": "49fb5b845b47930414721b698f5c4f18da5d07b58ded8f6d198db6538c010ed7",
      "executionMode": "native-subagents"
    }
  },
  "resolutions": {
    "resolutions": [
      {
        "issue": "evidence:evidence-01-phase-and-accounting",
        "decision": "applied",
        "reason": "Keep all six complete first-load observations and later cumulative checkpoints. No consent banner was observed; no-action checkpoints are not consent performance or causal savings."
      },
      {
        "issue": "evidence:evidence-02-eager-article-images",
        "decision": "applied",
        "reason": "Retain media-delivery as cantTell and the bounded loading/rendition investigation. Use measured image shares, preserve image usefulness and require a controlled comparison before asserting savings."
      },
      {
        "issue": "evidence:evidence-03-negotiated-image-format",
        "decision": "applied",
        "reason": "The media finding explicitly preserves working WebP negotiation; no format-conversion recommendation is warranted from .png URLs."
      },
      {
        "issue": "evidence:evidence-04-rendition-legibility-density",
        "decision": "applied",
        "reason": "Keep legibility and density unresolved. Report writer must present responsive renditions as a trial, not a proven reduction or mandatory resize."
      },
      {
        "issue": "evidence:evidence-05-live-versus-cold-theme",
        "decision": "applied",
        "reason": "Retain the narrow preference-behavior failure across six live-dark probes, and explicitly preserve successful cold-dark initialization and manual choices."
      },
      {
        "issue": "evidence:evidence-06-code-coverage-interpretation",
        "decision": "applied",
        "reason": "Unused-code and components remain unresolved; initial offsets are not transferable bytes or safe removal candidates."
      },
      {
        "issue": "evidence:evidence-07-cache-and-compression-boundaries",
        "decision": "applied",
        "reason": "Compression passes its narrow observed check; public-cache-policy remains unresolved without repeat-visit reuse and freshness validation."
      },
      {
        "issue": "evidence:evidence-08-resource-timing-zeros",
        "decision": "applied",
        "reason": "Use the staged CDP ledger for image traffic. Restricted Resource Timing zeros are not zero downloads."
      },
      {
        "issue": "evidence:evidence-09-journey-completion-scope",
        "decision": "applied",
        "reason": "Retain the successful desktop search journey as a scoped pass. Narrow layout and autocomplete remain distinct unresolved questions."
      },
      {
        "issue": "evidence:evidence-10-probe-scope-and-positive-behavior",
        "decision": "applied",
        "reason": "Retain scoped typography, reading-without-JavaScript and preference/motion observations. Layout/documents remain unresolved; no complete accessibility or lifetime notification claim is made."
      },
      {
        "issue": "evidence:evidence-11-search-metadata-applicability",
        "decision": "applied",
        "reason": "Retain the scoped metadata pass; deliberate search noindex does not require content-page canonical/description expectations."
      },
      {
        "issue": "evidence:evidence-12-source-and-technology-attribution",
        "decision": "applied",
        "reason": "Source review preserves clean revision but unverified deployment, metadata-only locks, heuristic technology detection and missing operational evidence."
      },
      {
        "issue": "claims:guide-discovery-scope",
        "decision": "applied",
        "reason": "Carbon-discovery fails only the declared discoverable-file check on the two tested 404 locations; disclosure-scope remains unresolved. No claim of high emissions or organization-wide policy absence."
      },
      {
        "issue": "claims:guide-hosting-unknown",
        "decision": "applied",
        "reason": "Hosting remains cantTell; CDN fingerprints and default carbon-model assumptions do not verify origin hosting."
      },
      {
        "issue": "claims:guide-model-boundary",
        "decision": "retained-with-reason",
        "reason": "Retain eligible deterministic per-visit Digital Carbon Ratings as modeled comparison grades, with complete protocol accounting, not measured annual emissions or certification badges. No annual scenario or measured energy is attached."
      },
      {
        "issue": "claims:guide-source-identity",
        "decision": "applied",
        "reason": "Keep revision and deployment caveats with source advice. Scoped source-code checks do not establish deployed behavior or visitor savings."
      },
      {
        "issue": "claims:guide-lock-validation",
        "decision": "applied",
        "reason": "Source-dependencies stays cantTell because lock contents were not captured. No vulnerability, outdated-package or removable-dependency claim."
      },
      {
        "issue": "claims:guide-runtime-and-ci-scope",
        "decision": "applied",
        "reason": "Runtime pass covers declaration consistency only. CI source failure describes a conditional duplicate-trigger path; recommendation first verifies actual paired runs/required checks and makes no energy claim."
      },
      {
        "issue": "claims:guide-maintenance-change-license",
        "decision": "applied",
        "reason": "Retain documented maintenance/contribution and licensing evidence at its stated scope; distinguish product release notes from deployment change history and avoid operational-execution claims."
      },
      {
        "issue": "claims:guide-budget-selection-limit",
        "decision": "applied",
        "reason": "Source-budgets remains cantTell. Request actual limits and owner/run receipts rather than declaring monitoring absent from a bounded selection."
      },
      {
        "issue": "claims:guide-ui-edit-prerequisites",
        "decision": "applied",
        "reason": "Keep autocomplete, code coverage and component optimization unresolved; no removal or restructuring is prescribed without task and deployed-implementation validation."
      },
      {
        "issue": "claims:guide-preferences-and-images-prerequisites",
        "decision": "applied",
        "reason": "Use six fresh live/cold observations for the theme defect; no exact local implementation fix is attested. Require legibility/density checks for image changes and preserve working font delivery."
      }
    ]
  },
  "reconciliationReceipt": {
    "resolutionsSHA256": "7629d15ec934036e7bbc284cad7650ed71423286c1c0db89cffb4da5f12555e7",
    "acceptedSHA256": {
      "evidence": "2b8b9da1bd6ea09d72d9eab8d4a7f77f8c386a2b8d8e024d26255be49a9be59e",
      "guidelines": "6df1e6f228656bbbaabec0aa8bd2b619c5e4152dbb618ec893205e07dad23664",
      "claims": "5cab552fbc17a301f32effa431bbea4af61d202f4946b097a6b9194fcad1ea40"
    },
    "next": "Coordinator writes review.json, preserving unresolved evidence; workflow score validates the final review. This receipt validates coverage of responses, not their semantic correctness."
  },
  "taskSHA256": {
    "guidelines": "9cc580bcc5fd94ed6791c4e2077085e70fac2a9f94f66cc857878ee4c8bf9a38",
    "evidence": "3f3e0ddd83aef6e623977b47f5b27949126d75e0f96cfb4a7606c517c729ec38",
    "claims": "3564a49602dcbd396aa75ee9516f85afff382361280840db0331ec47eef14f0d"
  },
  "finalReviewSHA256": "81b9b340955150748c990d2b225405e1d50a48e1d75ce91d26e73137bd511bcd",
  "finalReviewChange": "Unchanged guideline result after explicit reconciliation; reporting guidance retained separately."
}
