bingoss/owned-growth-engine
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Technical Audit shows health scores from normalized findings #3

New issue
Closed
opened 2026-05-28 18:14:26 +01:00 by bingoss · 1 comment
bingoss commented 2026-05-28 18:14:26 +01:00
Owner
Copy link

What to build

Type: AFK.

Extend the Technical Audit slice so the dashboard shows health scores derived from normalized Technical Findings. The score should summarize technical SEO/GEO readiness from actual findings and safe diagnostics, not guessed site quality.

Acceptance criteria

  • Technical Audit dashboard returns score data derived from normalized findings by severity, priority, and status.
  • Empty or unavailable finding data shows an unverified or unavailable state instead of a fake score.
  • Score output links back to the run/stage/finding evidence used to compute it.
  • Tests are written first for scored, empty, and unavailable evidence paths.

Blocked by

None - can start immediately

## What to build Type: AFK. Extend the Technical Audit slice so the dashboard shows health scores derived from normalized Technical Findings. The score should summarize technical SEO/GEO readiness from actual findings and safe diagnostics, not guessed site quality. ## Acceptance criteria - [ ] Technical Audit dashboard returns score data derived from normalized findings by severity, priority, and status. - [ ] Empty or unavailable finding data shows an unverified or unavailable state instead of a fake score. - [ ] Score output links back to the run/stage/finding evidence used to compute it. - [ ] Tests are written first for scored, empty, and unavailable evidence paths. ## Blocked by None - can start immediately
bingoss commented 2026-05-28 22:45:29 +01:00
Author
Owner
Copy link

Issue #3 completion audit

Requirements checked:

  • Dashboard score data is derived from normalized technical_findings severity, priority, and status via dashboard_technical_audit().health_score.
  • Empty finding data returns state: unverified and no fake numeric score.
  • Unavailable Postgres evidence returns state: unavailable and no fake numeric score.
  • Score evidence includes technical_finding_id, run_request_id, and run_stage_id links for the findings used in the score.
  • Tests were written first and cover scored, empty, and unavailable evidence paths.

Verification on codex-server:

  • python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_scores_normalized_findings tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_marks_empty_findings_unverified tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_marks_unavailable_evidence_without_fake_score -> OK
  • python3 -m unittest tests.test_technical_audit_worker -> 15 tests OK
Issue #3 completion audit Requirements checked: - Dashboard score data is derived from normalized technical_findings severity, priority, and status via dashboard_technical_audit().health_score. - Empty finding data returns state: unverified and no fake numeric score. - Unavailable Postgres evidence returns state: unavailable and no fake numeric score. - Score evidence includes technical_finding_id, run_request_id, and run_stage_id links for the findings used in the score. - Tests were written first and cover scored, empty, and unavailable evidence paths. Verification on codex-server: - python3 -m unittest tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_scores_normalized_findings tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_marks_empty_findings_unverified tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_technical_audit_dashboard_marks_unavailable_evidence_without_fake_score -> OK - python3 -m unittest tests.test_technical_audit_worker -> 15 tests OK
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
codex-token-write-test-1780004082
Temporary token write test; safe to delete.

No labels
codex-token-write-test-1780004082
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#3
No description provided.