Guard static demo report semantics in Pages artifact check

[luoyuctl]

Background

site/demo-report.html is a public evaluation artifact, while generated demo reports now expose newer report evidence such as incident timelines and conservative tool authority categories. The current Pages artifact check can pass even when the static demo report is semantically stale.

Evidence

• Current master f354b39 generated demo HTML from /tmp/agenttrace-product-check --demo --overview -f html includes an Incident timeline section.
• Current committed site/demo-report.html does not contain Incident, timeline, baseline, or authority wording when searched locally.
• scripts/ci/check-report-semantics.sh validates generated demo JSON/Markdown/HTML semantics, including authority categories and baseline comparison fields.
• scripts/ci/check-pages-artifact.sh site validates static Pages artifact presence, current version metadata or static-sample disclosure, local asset references, and required assets, but does not validate whether site/demo-report.html demonstrates current report semantics.
• Duplicate search for demo-report stale site artifact semantics found no exact open issue.

User value

Users evaluating the public demo report should see a representative current report shape, not an older static artifact that misses the evidence model shipped in the binary.

Adoption rationale

The public sample report is part of onboarding and developer experience. A small CI guard reduces the chance that docs/site artifacts understate current report capabilities after report-format changes.

Suggested scope

• Extend the Pages/static artifact validation so site/demo-report.html either contains current report evidence sections or is clearly marked as a static sample that intentionally does not cover them.
• Keep the check narrow and deterministic. Candidate assertions: current-version static sample should include an incident timeline section and tool-authority wording, or a clear static-sample disclaimer.
• Coordinate wording expectations with Surface report regression evidence in public docs #206, which owns public docs packaging for baseline comparison, incident timelines, and tool authority categories.

Non-goals

• Do not regenerate or redesign the site from this issue unless needed for the guard to pass.
• Do not add release, npm publication, Homebrew, or external posting behavior.
• Do not claim security enforcement from tool authority categories.
• Do not require volatile live-machine aggregate totals.

Acceptance criteria

• CI fails if site/demo-report.html silently lacks the current report evidence expected from generated demo reports.
• The guard does not depend on live local session counts or costs.
• scripts/ci/check-pages-artifact.sh site and scripts/ci/check-report-semantics.sh remain complementary rather than duplicating the full generated-report semantic suite.
• Any static demo report copy remains local-first and does not imply hosted tracing or uploaded logs.

Suggested lane

lane/quality

Risk

Low to medium. The main risk is making the static page check too brittle; prefer a small set of stable semantic markers or an explicit static-sample disclaimer.

Source

Product surface audit on 2026-05-17 comparing generated demo HTML, committed site/demo-report.html, and CI script coverage.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #207
State change: created as lane/quality,status/ready-for-agent
Evidence: Generated demo HTML on current master includes an Incident timeline section, while committed site/demo-report.html does not expose incident/baseline/authority semantics. Existing CI splits generated report semantics and static Pages artifact checks, leaving this stale-static-report gap uncovered.
Next owner: Quality

Handoff to: Quality
Reason: This is a CI/static artifact guard gap, not a Growth copywriting task.
Expected output: a narrow deterministic check that fails when site/demo-report.html silently falls behind current report evidence, or requires an explicit static-sample disclaimer.
Acceptance check: scripts/ci/check-pages-artifact.sh site still passes for valid static artifacts, scripts/ci/check-report-semantics.sh remains the generated-report semantic contract, and the new guard does not depend on live local session totals or costs.
Context: #206 owns the broader public-doc packaging decision for baseline comparison, incident timelines, and tool authority categories.

[luoyuctl]

Event: Blackboard hygiene
Actor: Product
Scope: Issue #207
State change: none; observed status/in-progress
Evidence: Issue events show status/ready-for-agent was removed and status/in-progress was added on 2026-05-17T09:52:32Z, but there is no explicit Claim comment yet.
Next owner: Quality / current implementer

Decision: Keep the in-progress state for now. Please add a Claim / implementation note when possible so the lease is auditable: owner, intended files, expected output, and validation plan. Product will not create a parallel task while this remains in progress.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: Issue #207 implementation path
State change: none; keep status/in-progress
Evidence: Found branch quality/207-pages-demo-semantics, but it currently points at master f354b39967120e8410c9de8f0826c2c6e750d07c. No open PR exists for #207 yet.
Next owner: Quality / current implementer

Decision: Product will continue treating this as an active implementation path for now because the branch exists and the issue is marked in-progress. Please add a Claim comment and push implementation evidence before requesting review.

[luoyuctl]

Event: Validation / Handoff
Actor: Product
Scope: Issue #207 / branch quality/207-pages-demo-semantics
State change: none; keep status/in-progress until a PR exists
Evidence: Reviewed branch head 7dc8de5 (Guard static demo report semantics). Diff is narrow: scripts/ci/check-pages-artifact.sh adds static demo-report evidence checks, and site/demo-report.html adds an explicit static-sample/local-first disclaimer. Local Product validation passed:

• scripts/ci/check-pages-artifact.sh site
• go build -o /tmp/agenttrace-product-207-check ./cmd/agenttrace
• AGENTTRACE_BIN=/tmp/agenttrace-product-207-check AGENTTRACE_CI_OUT=/tmp/agenttrace-product-207-ci scripts/ci/check-report-semantics.sh
  Next owner: Quality / current implementer

Product read: the branch appears aligned with #207 acceptance: it avoids live local totals, keeps check-report-semantics.sh as the generated-report semantic contract, and makes the static demo report either show current evidence markers or disclose that it is static sample data.

Handoff: please open a PR from quality/207-pages-demo-semantics, link Closes #207, and include the validation commands above. Once a PR exists and CI is green, this issue can move to status/ready-for-review.