feat(m-decomp): upgraded pipeline and added README, examples, and fixed module issues#676
feat(m-decomp): upgraded pipeline and added README, examples, and fixed module issues#676csbobby wants to merge 43 commits intogenerative-computing:mainfrom
Conversation
|
The PR description has been updated. Please fill out the template for your PR to be reviewed. |
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
|
|
There's an issue with our tests. CI pipeline won't pass. Will revisit this once that is fixed. It looks like the commit history and what not is fixed in this version of the PR, so we shouldn't have issues with merge conflicts. Thanks! |
|
I took a look at the impact on the docs, particularly API reference which is auto generated from teh code. (Errors/omissions are currently a soft warning, will become a hard CI failure soon -- check the 'Docs' 'Check' in the PR. Docstrings · CONTRIBUTING.md has more info Style note: use Google-style — We do have some other comments like this, but there's an issue to cleanup. For now the api doc builder transforms them so the api docs are ok. But project style is to use google. Missing / broken docstrings
Stale docs pagesThe output structure changed — files are now written to
|
|
Also noticed - The PR renames validation_strategy to val_strategy and adds two new fields val_fn and val_fn_name, but the Attributes: section in the docstring still documents only the old validation_strategy field. |
Type annotations & test coverageType annotations
TestsThe added tests cover The five new pipeline stage functions ( |
|
Hi @planetf1 this PR is to restore the changes on the PR 556 and handle several merge details. I currently updated the codes for the type annotations and will withhold the docstrings on a later checking. The tests are from another guy, I will also followup if they can take over.
|
Head branch was pushed to by a user without write access
Added tests and fixed bugs
M-Decompose Upgrade
Description
README and examples
m_decompose.Pipeline Stages
Constraint Extraction
Added whitespace canonicalization, separator unification, and newline-aware block segmentation to eliminate layout- and order-sensitive parsing failures. Produces stable constraint IDs and consistent downstream bindings, significantly improving subtask–constraint determinism and template reproducibility.
Inserted between constraint extraction and code generation, emitting a constraint to validation-type mapping (e.g., llm / code). Validation strategy is now a first-class, inspectable, template-addressable feature, enabling different generation paths per constraint type.
The validation_code_generator binds each constraint to a generated function stub in the V2. The CLI output shifts from a descriptive decomposition result to an importable, runnable validation module, allowing downstream systems to call validations directly and removing manual reinterpretation.
Implementation Checklist
Followed up all the updates of the PR with merging and handled the subsequent changes: #556
Protocol Compliance
parts()returns list of constituent parts (Components or CBlocks)format_for_llm()returns TemplateRepresentation or string_parse(computed: ModelOutputThunk)parses model output correctly into the specified Component return typeContent Blocks
Integration
mellea/stdlib/components/__init__.pyor, if you are adding a library of components, from your sub-moduleTesting
tests/components/