Skip to content

fix(verso): route project output to isolated fragment - #41

Merged
imathwy merged 1 commit into
mainfrom
fix/verso-project-output-routing
Sep 5, 2026
Merged

fix(verso): route project output to isolated fragment#41
imathwy merged 1 commit into
mainfrom
fix/verso-project-output-routing

Conversation

@imathwy

@imathwy imathwy commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Problem

Project finalizers configured VERSO_OUTPUT_DIR but the SDK only verified that path after running lake exe reasbook-site. Verso therefore wrote to its default _site directory, and the isolated fragment finalizer failed after otherwise successful generation.

Fix

  • pass the normalized output path as the generated Verso executable argv: --output PATH
  • reject ambiguous explicit output flags and non-executable targets
  • exercise the real SDK from the repository fragment test with a fake executable that only honors argv
  • document the output-isolation contract

Verification

  • Verso SDK: 34 tests
  • all capability SDK tests
  • repository tests: 50
  • SiFlow adapter tests: 175
  • ruff, Python compilation, and git diff checks

No Lean build was run locally. The remote release will reuse the immutable branch Lean caches.

@imathwy
imathwy merged commit a9c5c20 into main Sep 5, 2026
2 checks passed
@imathwy
imathwy deleted the fix/verso-project-output-routing branch September 5, 2026 21:15
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.

2 participants