# AC Evidence Bugfix Stories

Date: 2026-05-17
Source task: AC-EVIDENCE-BACKFILL-20260517

These bugfix stories come from the reconciled acceptance-criteria evidence batch.
They are current failures, not historical superseded criteria.

## BUG-DOCS-GENERATED-SITE-AC-20260517

Title: Fix docs adoption test after generated site content migration

As a product user evaluating first-run onboarding, I want the public site,
README, and adoption docs to consistently prove the first visible value path so
that documentation tests validate the real source of rendered content.

Acceptance criteria:

- `node --test test/docs-adoption.test.js` passes.
- The test validates `First visible value` in the generated site content source
  or rendered site output instead of requiring literal copy in `site/src/App.jsx`.
- README, adoption guide, core command surface, and site content still point to
  `orchestra workflow run --task DEMO-001 --gates none`.
- The governed production path remains documented.

## BUG-SITE-ARCH-DIAGRAM-RENDER-20260517

Title: Fix project site architecture diagram render

As a site visitor, I want the architecture viewer to render its SVG on desktop
and mobile so that the product architecture can be inspected visually.

Acceptance criteria:

- `npm run site:build` passes.
- `npm run test:e2e -- e2e/project-site.spec.js` passes.
- `[data-architecture-diagram] svg` becomes visible on desktop and mobile.
- Architecture controls remain interactive: zoom, pan, reset, node drag, and
  group drag.
- No console or page errors are emitted during diagram render.

## BUG-WEB-OPS-READINESS-COPY-20260517

Title: Restore release readiness state in task detail

As an operator using the web console, I want task detail to show release
readiness state consistently so that I can understand whether a task is ready or
what remains unresolved.

Acceptance criteria:

- `npm run test:e2e -- e2e/web-console.spec.js` passes the WEB-OPS scenario.
- Task detail for `OPS-E2E` shows an explicit positive release readiness state
  or the E2E is updated to assert the current accepted copy.
- Task detail still shows acceptance criteria, Definition of Ready, Definition
  of Done, handoffs, reviews, and evidence.
- Negative readiness state for `COST-E2E` still surfaces missing backlog item
  and release-readiness remediation.

## BUG-WEB-LIFECYCLE-BLOCK-GATE-20260517

Title: Restore web lifecycle block gate control after request changes

As a release reviewer using the web console, I want to approve, request changes,
or block a workflow gate from the same lifecycle surface so that gate decisions
remain auditable and actionable.

Acceptance criteria:

- `npm run test:e2e -- e2e/web-console.spec.js` passes the WEB-LIFECYCLE scenario.
- After a `Request Changes` decision, the gate decision surface still exposes a
  valid block path or the workflow state transition intentionally removes block
  and the test documents the accepted behavior.
- Gate history records `changes`, `block`, and `approve` decisions when those
  actions are available.
- Resume continues from the approved gate and completes the lifecycle.