Fix/output multiplicity pipe sequence

[thomashebrard]

🔗 Related Issues

📝 Description

🔄 Type of Change

• 🐛 Bug fix
• ✨ New feature
• 💥 Breaking change
• 📚 Documentation update
• 🧹 Code refactor
• ⚡ Performance improvement
• ✅ Test update

🧪 Tests

📋 Checklist

• Linting / type-checking / unit tests pass locally with my changes
• I've added tests that prove my fix is effective or that my feature works
• My code follows the style guidelines of this project
• I've made corresponding changes to the documentation
• My changes generate no new warnings

---

Note

Validate PipeSequence output multiplicity against last step using new compatibility helper; refine batch/sub-pipe param handling and pretty rendering for text.

• Pipes / Controllers:
  • PipeSequence: Validate output using concept compatibility and is_multiplicity_compatible, considering per-step overrides and batching; improved error messages.
  • SubPipe / PipeBatch: Propagate batch_params only when batching; create ad-hoc batch pipe code (<pipe>_adhoc_batch); in batch branches set final_stuff_code and force single per-branch output via output_multiplicity=False.
  • SubPipeFactory: Compute output_multiplicity directly (handles batch_over/batch_as, nb_output, multiple_output).
• Core:
  • variable_multiplicity: Add is_multiplicity_compatible utility.
  • concept_factory: For string-declared concepts, stop setting refines.
  • TextContent: Implement rendered_pretty via rich.markdown.Markdown and remove inline pretty print.
• Tests:
  • Add unit tests for is_multiplicity_compatible.
  • Expand integration tests for PipeSequence multiplicity scenarios and Discord newsletter batching (plus sample test data).
• Misc:
  • Update VS Code launch configs (debugging presets).

^{Written by Cursor Bugbot for commit 63c4b28. This will update automatically on new commits. Configure here.}