Skip to content

Trace size limit switch on the Deploy step; pin DirXMLDev 0.64.0 - #184

Merged
jcombs-pointblue merged 1 commit into
mainfrom
trace-size-limit-switch
Nov 3, 2026
Merged

jcombs-pointblue merged 1 commit into
mainfrom
trace-size-limit-switch

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

Core 0.64.0 records each driver's trace size limit in the tree. A new driver gets the limit and its trace level and file. An existing driver keeps the vault's limit unless vault.deploy --trace-size-limit is given.

  • Deploy step: a new switch, write the tree's trace size limits over the vault's. Changing it marks the plan out of date like the other options.
  • API: traceSizeLimit on plan and deploy requests.
  • Agent tools: plan_deploy and deploy take traceSizeLimit. Documented in agents.md and features.md.
  • Version: pins core 0.64.0 and bumps to 0.87.0.

Checked

  • Server build and tests, vitest and the type-checked page build all pass.
  • On a local server, using a scratch copy of the refreshed edir3 tree with the AD limit set to 100000, against edir3 and with nothing deployed:
    • Compare showed ~ trace-size-limit: 200000 -> 100000.
    • Plan without the switch: 0 steps, with a note that the vault keeps its value.
    • Plan with the switch: one modify DirXML-TraceSizeLimit = 100000 (was 200000), 0 restarts.

🤖 Generated with Claude Code

Write the tree's trace size limits over the vault's (vault.deploy
--trace-size-limit) as a Deploy step option and as traceSizeLimit on the
plan_deploy and deploy agent tools.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jcombs-pointblue
jcombs-pointblue merged commit 95944cb into main Nov 3, 2026
2 checks passed
@jcombs-pointblue
jcombs-pointblue deleted the trace-size-limit-switch branch November 3, 2026 00:13
jcombs-pointblue added a commit that referenced this pull request Nov 3, 2026
Trace size limit switch on the Deploy step; pin DirXMLDev 0.64.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant