Skip to content

Harden writing pipeline: warning vs error distinction, flexible file structure#14

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

Harden writing pipeline: warning vs error distinction, flexible file structure#14
CMander02 wants to merge 1 commit intoziyan-todo-4from
ziyan-todo-7

Conversation

@CMander02
Copy link
Copy Markdown
Collaborator

Summary

  • sections/ directory no longer required — single-file main.tex is valid
  • build_log.txt missing with PDF present is now a warning, not a blocking error
  • citation_verification.json and self_review.json missing are now warnings
  • Manager separates [warning] from errors: warnings display but don't trigger repair
  • Prompt updated with explicit .bib guidance and JSON schema for verification artifacts

Context

Example run produced a single-file main.tex without sections/, used inline \begin{thebibliography} instead of .bib, and lacked build_log.txt. Validation triggered unnecessary repair cycles for issues that weren't real blockers.

Depends on #13.

Test plan

  • 5 new tests + 2 updated tests in tests/test_writing_pipeline.py — all passing
  • Verify existing test_stage07_validation_passes_with_expected_outputs still passes

🤖 Generated with Claude Code

…structure

- sections/ directory no longer required (single-file main.tex is valid)
- build_log.txt missing with PDF present is now a warning, not a blocking error
- citation_verification.json and self_review.json missing are now warnings
- Manager separates [warning] from errors: warnings display but don't trigger repair
- Prompt updated: explicit .bib guidance, JSON schema for verification artifacts
- 5 new tests, 2 existing tests updated for warning/error distinction

Addresses TODO 7 (V7-1 through V7-4) 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