Confluence browser
confluence/index.htmlscreenshots/confluence-browser-desktop-1440.pngImplementation evidence
Screenshots, manifests, and readiness in reach.
The workbench exposes build evidence from the preview bundle, manifest, screenshots, generated indexes, and readiness summary. Planning evidence now lives on Forgejo issues and their linked PRs, comments, and artifacts.
- Bundle
- artifact
- Routes
- 12
- Viewports
- 3
- Issue flow
- Forgejo
Visual proof
Preview screenshots render before paths.
The gallery reads the preview evidence manifest when it exists and keeps browser-unavailable placeholders explicit. Paths remain available as trace metadata rather than becoming the main review surface.
- Manifest
.reports/preview-evidence/manifest.json- Mode
- waiting-for-preview-evidence
- Commit
- build pending evidence capture
- Generated
- created by npm run evidence:preview
Vault architecture
vault/n/20-architecture/platform/openshift-concept-overview/index.htmlscreenshots/vault-architecture-mobile-390.pngIssue evidence
Where to inspect implementation proof
Build evidence still comes from `.reports/preview-evidence/`. Work-item evidence now belongs to Forgejo issue comments, linked pull requests, CI runs, and the issue-agent report artifact.
| Evidence | Location | Purpose |
|---|---|---|
| Issue discussion | Forgejo issues | Planning, scope tuning, implementation notes, and acceptance history. |
| Issue-agent report | .reports/issue-agent/issue-agent-report.json | Automation trigger payload and dry-run/OpenCode execution result. |
| Preview bundle | .reports/preview-evidence/manifest.json | Portal screenshots, generated indexes, readiness summary, and visual QA metadata. |
Planning evidence
Issues point to proof
New work items should keep acceptance criteria and implementation commentary on the issue, then link pull requests and CI artifacts back to that issue.
- AcceptanceKeep checklist state on the Forgejo issue.
- ImplementationUse issue-linked branches and pull requests by default.
- AutomationUse
agent/implementto start the issue-agent workflow.
Activation boundary
Fixture evidence is not live access.
The issue workflow does not authorize real RWS content exposure, authenticated preview access, live infrastructure changes, or Confluence writes. Those paths still require separate human approval and proof.
Exposure and cleanup review gates
- Review token scope, event trust, and fork behavior before enabling PR comment writes.
- Review screenshots, generated indexes, readiness summaries, preview URLs, and branch metadata before real RWS content enters artifacts.
- Prove preview resource creation, authenticated access, retention, and cleanup before sharing colleague-facing previews.
- Keep Confluence staging disabled until draft permissions, version conflicts, and rollback behavior are reviewed.