Skip to content

Add dissemination readiness check: structured warnings before final approve#15

Open
CMander02 wants to merge 1 commit intoziyan-todo-7from
ziyan-todo-8
Open

Add dissemination readiness check: structured warnings before final approve#15
CMander02 wants to merge 1 commit intoziyan-todo-7from
ziyan-todo-8

Conversation

@CMander02
Copy link
Copy Markdown
Collaborator

Summary

  • Add validate_dissemination_readiness() checking PDF, main.tex, reviews, and readiness_report.json
  • Stage 08 approve now shows readiness warnings and requires yes confirmation
  • readiness_report.json blocking gaps are surfaced as warnings to the user
  • Prompt requires readiness_report.json with blocking_gaps/warnings schema

Context

Example run's Stage 08 identified 4 blocking gaps (missing baselines, missing splits, abstract too long, no figure scripts) but the user could approve without any warning. The system now surfaces these as structured warnings before final approval.

Depends on #14.

Test plan

  • 7 new tests in tests/test_dissemination.py — all passing
  • Manual: --fake-operator full run → Stage 08 approve → verify warning display

🤖 Generated with Claude Code

…pprove

- Add validate_dissemination_readiness() checking PDF, main.tex, reviews, readiness_report.json
- Stage 08 approve now shows readiness warnings and requires 'yes' confirmation
- readiness_report.json blocking_gaps are surfaced as warnings to the user
- Prompt updated to require readiness_report.json with blocking_gaps/warnings schema
- 7 new tests covering all warning scenarios

Addresses TODO 8 (V8-1 through V8-2) from vulnerability analysis.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant