From 106dc86f80c313b88079e3ecb4a636aa1f36997f Mon Sep 17 00:00:00 2001 From: Atlas from Plumb Date: Thu, 15 Oct 2026 06:57:03 +1100 Subject: [PATCH 1/2] docs(site): name context_for_task in the Map card, as experimental MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The site counted context_for_task in "Sixty structured tools" and in Map ×9 but never named it. The Map card now lists it and says, in one sentence backed by the 0.24.1 CHANGELOG entries, what the pack carries: the seeds' code, callers and related declarations, the tests that reach them (#647), whether a Go caller list is complete (#648/#651), and a note while the index is still on its first pass (#668). Co-Authored-By: Claude Opus 5.5 Plumb-Session: forest-ridge --- site/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/index.html b/site/index.html index 5a3c9933..be86521f 100644 --- a/site/index.html +++ b/site/index.html @@ -451,7 +451,7 @@

Eight capabilities.

Understand×8

Jump to any definition, list every caller, walk the type tree; answers from the compiler itself, never a text-search guess.
  • find_references
  • call_hierarchy

Edit*×13

Rename across the whole codebase, apply multi-file changes in one atomic step, delete safely. It all lands, or nothing does.
  • rename_symbol
  • transaction_apply*

Read×9

Pull exactly what you need: a single symbol, a line range, a glob, or a diff, instead of dragging a whole file into context.
  • read_symbol
  • file_outline
-

Map*×9

Search the repo, trace what a change touches, and get the precise tests to run; in milliseconds, even while the code won’t compile.
  • topology_impact*
  • topology_affected
+

Map*×9

Search the repo, trace what a change touches, and get the precise tests to run; in milliseconds, even while the code won’t compile. Experimental: context_for_task starts from the files or symbols an agent names and returns one bounded pack; their code, callers and related declarations, the tests that reach them, whether a Go caller list is complete, and a note while the index is still being built.
  • topology_impact*
  • topology_affected
  • context_for_task*

Recall×9

Durable per-repo memory the agent can write to, plus a typed, shell-free git that keeps every commit clean.
  • write_memory
  • git

Coordinate*×4

The layer above the locks: an agent-to-agent mailbox, peer awareness and durable findings, so a fleet hands off work instead of duplicating it.
  • leave_note
  • share_findings*

Tasks & config×4

Run the repo’s own build, test, lint and mutation-test commands; no shell, bounded; and let the agent set task and config keys within a user-controlled allowlist.
  • run_task
  • mutation_test
From 5e7510f53ad5ee73371401467fbb900364dd9706 Mon Sep 17 00:00:00 2001 From: Atlas from Plumb Date: Thu, 15 Oct 2026 07:01:33 +1100 Subject: [PATCH 2/2] docs(site): keep "in milliseconds" off context_for_task; state its 2 s deadline MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review of #669: the new sentence followed "in milliseconds" and could read as covered by it, but the pack's graph walk runs under a 2 s deadline (docs/tools.md § context_for_task). Name it as a separate call, and say so. Co-Authored-By: Claude Opus 5.5 Plumb-Session: forest-ridge --- site/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/index.html b/site/index.html index be86521f..5851574f 100644 --- a/site/index.html +++ b/site/index.html @@ -451,7 +451,7 @@

Eight capabilities.

Understand×8

Jump to any definition, list every caller, walk the type tree; answers from the compiler itself, never a text-search guess.
  • find_references
  • call_hierarchy

Edit*×13

Rename across the whole codebase, apply multi-file changes in one atomic step, delete safely. It all lands, or nothing does.
  • rename_symbol
  • transaction_apply*

Read×9

Pull exactly what you need: a single symbol, a line range, a glob, or a diff, instead of dragging a whole file into context.
  • read_symbol
  • file_outline
-

Map*×9

Search the repo, trace what a change touches, and get the precise tests to run; in milliseconds, even while the code won’t compile. Experimental: context_for_task starts from the files or symbols an agent names and returns one bounded pack; their code, callers and related declarations, the tests that reach them, whether a Go caller list is complete, and a note while the index is still being built.
  • topology_impact*
  • topology_affected
  • context_for_task*
+

Map*×9

Search the repo, trace what a change touches, and get the precise tests to run; in milliseconds, even while the code won’t compile. A separate, experimental call, context_for_task, takes the files or symbols an agent names and returns one bounded pack: their code, callers and related declarations, the tests that reach them, whether a Go caller list is complete, and a note while the index is still being built. Its graph walk stops at a 2 s deadline.
  • topology_impact*
  • topology_affected
  • context_for_task*

Recall×9

Durable per-repo memory the agent can write to, plus a typed, shell-free git that keeps every commit clean.
  • write_memory
  • git

Coordinate*×4

The layer above the locks: an agent-to-agent mailbox, peer awareness and durable findings, so a fleet hands off work instead of duplicating it.
  • leave_note
  • share_findings*

Tasks & config×4

Run the repo’s own build, test, lint and mutation-test commands; no shell, bounded; and let the agent set task and config keys within a user-controlled allowlist.
  • run_task
  • mutation_test