docs: remove tracked planning and architecture records (#12856)

This commit is contained in:
morluto authored and GitHub committed 2026-11-20 09:47:41 -05:00
1 parent 42b36e200b
commit a1dec2d2d5
362 files changed
+119 -18521

No files matched your search

+2 -1
View File
@@ -94,7 +94,8 @@ raising a REA startup or operation deadline, separately ensure the client allows
enough time for the full request. Use `inspect_analysis_settings` for the running
server's defaults; `rea doctor` checks launch configuration and cannot observe
another process's runtime overrides. See the
[settings design](../design/limits-and-recovery.md) for ownership and lifetime.
[analysis settings and recovery](../reference/limits-and-recovery.md#precedence-and-lifetime)
for precedence and lifetime.
## Client tool names and discovery
+1 -1
View File
@@ -1563,7 +1563,7 @@ invocation instead. In MCP, `ghidra.decompile_timeout_seconds` can override the
value for newly accepted operations on the existing Program; explicit `null`
removes the deadline. A transient timeout remains uncached so the same function
can be retried after an update. See the
[settings design](../design/limits-and-recovery.md#runtime-settings-through-mcp).
[analysis settings and recovery](../reference/limits-and-recovery.md#runtime-settings-through-mcp).
Codex/Kimi registrations derived by `rea setup` add the selected launch value
to the tool deadline as a single-decompile estimate; a runtime update does not
change that registration. A bulk call can need that limit for