Parent: #421
Depends on: #423
Provider candidate: https://github.com/ifrost/afterwriting-labs
Outcome
Adopt/adapt/reject the afterwriting CLI as a focused Fountain publication/report provider.
Observed upstream CLI/docs support Fountain → formatted PDF through Node.js and screenplay analysis/statistics. The upstream CLI documentation explicitly notes direct FDX conversion is not reliable, so FDX normalization should use the screenplay interchange provider rather than pretending afterwriting owns it.
Requirements
- Evaluate current package/release/runtime support and MIT licensing.
- Register Node/runtime and afterwriting provider requirements explicitly.
- Expose Fountain → screenplay PDF as a typed, validated capability.
- Evaluate useful deterministic analysis outputs such as page count, locations, character/dialogue/action statistics; expose only stable proven outputs.
- Bind PDF generation options (paper/profile, title page, page numbers, scene numbering, fonts, etc.) to a versioned Renderflow profile.
- Run with direct argv and bounded process controls.
- Validate produced PDF independently and retain screenplay/source/provider provenance.
- Keep provider-specific formatting options out of core screenplay semantics.
Acceptance criteria
Non-goals
Replacing general Pandoc PDF rendering or using afterwriting as the screenplay interchange layer.
Provider observation — 2026-09-25
The current public afterwriting-labs README/docs describe an MIT-licensed, Node.js-based CLI for Fountain → PDF plus screenplay statistics/reporting. Its CLI documentation explicitly lists direct FDX conversion as a known issue, so FDX normalization must not be assigned to this provider without new execution evidence.
Re-verify package/runtime health and current maintenance before adopting it as a supported provider.
Parent: #421
Depends on: #423
Provider candidate: https://github.com/ifrost/afterwriting-labs
Outcome
Adopt/adapt/reject the afterwriting CLI as a focused Fountain publication/report provider.
Observed upstream CLI/docs support Fountain → formatted PDF through Node.js and screenplay analysis/statistics. The upstream CLI documentation explicitly notes direct FDX conversion is not reliable, so FDX normalization should use the screenplay interchange provider rather than pretending afterwriting owns it.
Requirements
Acceptance criteria
Non-goals
Replacing general Pandoc PDF rendering or using afterwriting as the screenplay interchange layer.
Provider observation — 2026-09-25
The current public
afterwriting-labsREADME/docs describe an MIT-licensed, Node.js-based CLI for Fountain → PDF plus screenplay statistics/reporting. Its CLI documentation explicitly lists direct FDX conversion as a known issue, so FDX normalization must not be assigned to this provider without new execution evidence.Re-verify package/runtime health and current maintenance before adopting it as a supported provider.