Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
Track the gitignored files a fresh worktree of this repo needs (#1183)
Louis Choquelbd70273acf2d
diff --git a/.gitignore b/.gitignoreindex a95df5e3f..999d3ddd6 100644--- a/.gitignore+++ b/.gitignore@@ -44,7 +44,6 @@ reports/results/# personnal pipelex config files that overrides the default one-.worktreeincludepipelex_super.tomlpipelex_override.tomlpipelex_temporary_override.tomldiff --git a/.worktreeinclude b/.worktreeincludenew file mode 100644index 000000000..080b6ba52--- /dev/null+++ b/.worktreeinclude@@ -0,0 +1,7 @@+# .worktreeinclude — the gitignored files a fresh worktree of this repo needs.+# Read by Claude Code for its own worktrees and by `wt` for ours.+.env+.pipelex/pipelex_override.toml+.pipelex/telemetry_override.toml+.pipelex/pipelex_service.toml+.pipelex-dev/test_profiles_override.tomldiff --git a/CHANGELOG.md b/CHANGELOG.mdindex 2508e2915..8ae4ea978 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,7 @@### Added+- **`.worktreeinclude`**: the gitignored files a fresh worktree of this repo needs — `.env`, the three `.pipelex/*.toml` overrides and `.pipelex-dev/test_profiles_override.toml` — are now declared in a tracked file at the repo root instead of living in one contributor's shell script. Claude Code reads it when it creates a worktree with git, and the workspace's `wt` tool reads it for the durable ones, so a fresh worktree of `pipelex` arrives configured either way. The file holds only the names of untracked files this repo's `.gitignore` already discloses, never their contents; it was previously gitignored here, which made the mechanism personal and untracked before anyone had used it.- **`pipelex-dev generate-projection-corpus`**: The generator of the shared fixture corpus that pins the two client-side inputs-template projections — the TypeScript one in `mthds` and its Python twin — against each other. Each client SDK now renders a pipe's fill-in template from the input-form descriptor it already has instead of asking a server for one, so the two renderings have to agree exactly, TOML `# concept:` comment lines included. The command pairs each pipe's descriptor with the expected template in both shapes (compact and explicit) and both formats (JSON and TOML), and records where that expectation deliberately differs from this engine's own inputs-template renderer: the expectation is authored from a reference projection that walks the descriptor, where the engine reflects the runtime content classes. Each class of difference is declared rather than discovered — an undeclared one fails the run, and so does a declared one that no longer occurs, so an engine fix retires its entry deliberately. A new corpus bundle covers what the existing probe bundles did not: a text field merely named `url` beside a real file position, optional file fields nested inside a structure, and both a fixed `[N]` and a variable `[]` slot over a structured concept. See [Projection Fixture Corpus](contribute/generate-projection-corpus.md).- **The projection corpus round-trips every template it pins through the input shaper**: `pipelex-dev generate-projection-corpus` now hands each projected template straight back to the runtime — both shapes, assembled exactly as an entry-pipe run assembles a caller's inputs — because a fill-in template exists to be filled in and run, and nothing checked that before. Twice the corpus pinned slots the runtime rejects outright and a human review round caught it rather than the capture; the second time the divergence gate absorbed the broken sites into a declared class and exited zero, since "differs from the engine" and "the engine refuses this value" are different questions. The verdict follows the same declared-never-discovered discipline as the divergence record, through an `EXPECTED_UNSHAPEABLE` registry mapping a pipe and shape to the item tracking the gap: an undeclared refusal fails the command naming the pipe, shape and error, a declared entry whose template has started shaping fails it too so a fix retires its declaration deliberately, and a declared one is stated in the manifest as an `unshapeable` entry carrying the contract-stable error class and its ledger item — so a known-open gap is recorded rather than blocking the capture. See [Projection Fixture Corpus](contribute/generate-projection-corpus.md).- **Include a method by address — fetch-on-miss**: a bundle referencing another method by address (`github.com/...->domain.pipe`) that misses the installed methods now fetches the package by reference — honoring an `@<tag>` pin, through the same grammar, bounds, and tags-only rules as a direct fetch, with the same hosted-parity warning for Python structure classes locally and a hard refusal on sandbox-hosted deployments — installs it into `~/.mthds/methods/` (atomic staging write, `.git/` stripped, fetch provenance recorded beside the manifest in a `.provenance.json` sidecar: address, tag, and the resolved commit SHA), and loads it so resolution proceeds. Once installed, the method is reused and the network is never touched again — including for a reference pinning a different tag, which warns and uses the installed copy. The former silent-miss warning in the library manager is now a real diagnostic: a miss that cannot be bridged (fetch disabled via the new `[interpreter.methods] fetch_on_miss` config or the `PIPELEX_METHODS_FETCH_ON_MISS` environment variable, an unfetchable address, or a failed fetch) raises an error naming the address and the remedy, never a silent pass. The install target is guarded by identity: two packages sharing a bare directory name but coming from different addresses collide with a loud error naming both addresses (never a silent load of the wrong package, never an overwrite), a concurrent install of the same package is tolerated (each attempt stages under a unique dot-prefixed directory, and losing the final rename race to a matching occupant uses the winner's copy), and a fetched package containing a symlink is refused outright, since a link's target would bypass the content scans. Installed-method lookup by full address is now case-insensitive, matching GitHub's owner/repository semantics and the fetch path's manifest-identity matching, and discovery skips dot-prefixed directories. See [Packages → Include by Address](building-methods/packages.md) and [Methods Configuration](configuration/config-practical/methods-config.md).