Technical Audit creates coding-agent handoff artifacts with verification steps #12

Closed
opened 2026-05-28 18:14:42 +01:00 by bingoss · 1 comment
Owner

What to build

Type: AFK.

Extend the Technical Audit Specialist output so actionable website/code findings can produce a Reviewable Artifact that is ready for a coding agent. The artifact must include acceptance criteria and verification steps, but must not edit the website, deploy, or open a pull request.

Acceptance criteria

  • Actionable findings that need coding-agent work can produce one Reviewable Artifact with main and technical-handoff links.
  • The handoff includes affected URLs, evidence, recommended fix, acceptance criteria, and verification method.
  • The Review Board shows the handoff for Josh approval without raw provider payloads or guessed facts.
  • Tests are written first for handoff creation, insufficient evidence blocking, and approval-boundary enforcement.

Blocked by

None - can start immediately

## What to build Type: AFK. Extend the Technical Audit Specialist output so actionable website/code findings can produce a Reviewable Artifact that is ready for a coding agent. The artifact must include acceptance criteria and verification steps, but must not edit the website, deploy, or open a pull request. ## Acceptance criteria - [ ] Actionable findings that need coding-agent work can produce one Reviewable Artifact with main and technical-handoff links. - [ ] The handoff includes affected URLs, evidence, recommended fix, acceptance criteria, and verification method. - [ ] The Review Board shows the handoff for Josh approval without raw provider payloads or guessed facts. - [ ] Tests are written first for handoff creation, insufficient evidence blocking, and approval-boundary enforcement. ## Blocked by None - can start immediately
Author
Owner

Issue #12 completion audit

Implemented and verified:

  • Technical Audit Specialist now writes one technical_fix_handoff Reviewable Artifact with requested_action approve_for_handoff.
  • The artifact gets two local-path artifact links: main summary and technical_handoff markdown.
  • The technical_handoff markdown is generated from normalized Technical Findings and includes affected URL, issue type, severity, priority, evidence, recommended fix, safe implementation boundary, acceptance criteria, and verification method.
  • Insufficient normalized evidence now blocks safely before artifact/link creation.
  • Approval boundary is enforced: the specialist stops at a pending Reviewable Artifact and creates no handoff_creation run, CMS draft, deployment, website edit, or pull request side effect.
  • Review Board shows the handoff card and links without raw provider payloads or long artifact bodies.

Tests run on codex-server:

  • python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker
  • Result: 44 tests OK
Issue #12 completion audit Implemented and verified: - Technical Audit Specialist now writes one technical_fix_handoff Reviewable Artifact with requested_action approve_for_handoff. - The artifact gets two local-path artifact links: main summary and technical_handoff markdown. - The technical_handoff markdown is generated from normalized Technical Findings and includes affected URL, issue type, severity, priority, evidence, recommended fix, safe implementation boundary, acceptance criteria, and verification method. - Insufficient normalized evidence now blocks safely before artifact/link creation. - Approval boundary is enforced: the specialist stops at a pending Reviewable Artifact and creates no handoff_creation run, CMS draft, deployment, website edit, or pull request side effect. - Review Board shows the handoff card and links without raw provider payloads or long artifact bodies. Tests run on codex-server: - python3 -m unittest tests.test_site_crawler tests.test_technical_audit_worker - Result: 44 tests OK
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bingoss/owned-growth-engine#12
No description provided.