feature/Integrate-docs-follow-tree · L-261017-9bdb38

Merged
LC
7d ago
+58112-27553

pipelex-integrate's call sites and their prepareInputs pointers now send the method's tree as the MTHDS files map, in TypeScript and in Python, and the skill stops when a METHODS.toml lies above the bundle. The validation hook is re-vendored onto @pipelex/sdk 0.48.1, which sends the tree and keeps files that look like keys or credentials on the machine. The hook docs, the README and the hook tests say exactly what travels and what stays home.

Closes L-261017-9bdb38
Closes L-260913-6cac17
Leaves L-261022-e15b5d

🤖 Generated with Claude Code


Summary by cubic

pipelex-integrate call sites now send the method's whole bundle directory as the method's tree (directory: BUNDLE_DIR in TypeScript, tree=BUNDLE_DIR in Python) instead of a .mthds files list plus a template resources map, so files a bundle's PipeDocGen steps name travel in both languages. The validation hook is re-vendored onto @pipelex/sdk 0.48.1, which sends the same tree and keeps key- or credential-like files on the machine. The skill stops when a METHODS.toml lies above the bundle.

Migration

  • Both SDK floors move to 0.48.0; mthds_contents, resources, and the call site's template-file helpers are gone.
  • A refresh raises the pin and rewrites a module that still sends the retired fields.
  • Python projects on an older pipelex-sdk keep the old module, and the skill stops over a templated bundle there.

Hook and drift gates

  • The hook's validate stage sends the edited method as the tree after a version handshake, and files that look like keys or credentials stay home under a non-blocking note.
  • Both gates list the tree with the MTHDS standard's lister; a METHODS.toml above bundle_dir roots the tree there, reported with cures instead of a refresh hint.
  • The TypeScript gate finds that lister beside @pipelex/sdk and, under Yarn Plug'n'Play, resolves it through pnpapi.
  • Hook docs, the README, and the tests pin exactly what travels and what stays home.