feat: Loom spine — LOOM_TASK_ID binding + pack --external (0.26.3)#51
Merged
Conversation
When the MCP runs inside a Loom task session (LOOM_TASK_ID set), task_create resolves/creates ONE journal per board task, tagged with a 'loom:<id>' external reference, so every task_create call (and the whole pipeline) shares the same journal — the agent's reasoning lands on the board task's history. Adds db::task_id_by_external for idempotent resolution. Env-gated: without LOOM_TASK_ID, behavior is unchanged. Additive + tested (db + mcp suites green).
pack now accepts --external (e.g. loom:t-abc) to render a task's dossier by its external reference instead of its tj id, so a consumer that only knows the board task id can fetch its journal. task_id becomes optional; positional id still works unchanged. Tested.
- rebased 2 Loom commits (LOOM_TASK_ID spine + pack --external) onto main 0.26.2 — dropped already-merged ask --json + clean-pack dupes - cargo fmt on cli main.rs + mcp main.rs (long lines) - fix clippy unnecessary_to_owned in db.rs test - bump workspace 0.26.3, CHANGELOG added Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two additive features that wire Task-Journal into the Loom board host.
tj-mcp): when the MCP runs inside a Loom tasksession (
LOOM_TASK_IDenv var set),task_createresolves or creates ONEjournal keyed by an
loom:<id>external reference — alltask_createcallsin the pipeline share the same journal, so the agent's reasoning lands on the
board task's history. Without
LOOM_TASK_IDbehavior is unchanged.pack --external(tj-cli):task-journal pack --external loom:t-abcrenders a resume pack by external reference instead of
tjid, so a consumerthat only knows the board task id can fetch its journal.
Rebased from stale 0.25.1 base onto current main (0.26.2), bumped to 0.26.3.
Fixes:
cargo fmt, clippyunnecessary_to_ownedin db test.Type of change
Test plan
task_id_by_external_resolves_exact_token— db-level unit testcargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningscargo test --workspace --all-targets(all green)RUSTDOCFLAGS=-D warnings cargo doc --workspace --no-depsCHANGELOG
## [0.26.3]entry (Added)