Repository navigation
maple-agent: add a scenario checklist and a short performance check - #1099
Open
AnthonyRonning wants to merge 2 commits into
Open
AnthonyRonning wants to merge 2 commits into
AnthonyRonning wants to merge 2 commits into
Conversation
AnthonyRonning
added this pull request to stack #1092
October 7, 2026 15:36
AnthonyRonning
marked this pull request as ready for review
October 7, 2026 15:36
AnthonyRonning
force-pushed
the
agent-trim/checklist-perf
branch
from
October 7, 2026 19:54
a768528 to
adb3522
Compare
AnthonyRonning
changed the title
Two documents and one script for the trimmed build. The scenario checklist has one scenario per feature that carries over to the next runtime, marks the ones the runtime tests already cover, and keeps a results table; it ran on this build and runs again on the new runtime before that merges. The performance check is a smoke and sanity check, not a gate: cold start to an interactive window from the app's own startup markers, resident memory at idle and after a long task, and a by-hand note on whether a long streamed answer stays smooth. The numbers recorded here come from a release build on the machine named in the document and are to be repeated on the same machine before the swap merges. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The performance check now asks for three things on a release build: the time to an open window, memory after a long streamed answer, and whether streaming stays smooth. The script and the extra startup and idle numbers go. The scenario checklist drops its planning-stage name, cites the build it ran on, and no longer claims that a background-completion test covers Ctrl/Cmd+Enter steering. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STEaSNTNUiiNNLXcKidE2d
AnthonyRonning
force-pushed
the
agent-trim/checklist-perf
branch
from
October 7, 2026 20:36
adb3522 to
884dafe
Compare
This branch has not been deployed
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
2 participants
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.
Layer 9 of 9 in the Maple Agent approvals-and-subagents removal stack (base:
agent-trim/docs-sweep, PR #1098). Docs only.What changes
docs/scenario-checklist.md: one scenario per user-facing feature (tasks, composer, slash commands and skills, tools, external agents, computer use, MCP, ACP and command line, side models, the rest), each with how to run it and what passing looks like. Scenarios the runtime tests cover name the covering test. A results table records each run.docs/performance-check.md: a quick release-build sanity check, not a gate. It records the time to an open window, memory after a long streamed answer, and whether streaming stays smooth, compared on the same machine before and after a runtime change.Validation
just ciin the component Nix shell: green (docs only; Agent CI's change detection skipsdocs/).93a235d2): 15 scenarios passed on that build, 13 more passed earlier the same day on debug builds of the stack, and 10 are not run yet (listed in the results row with the reason). No scenario failed.🤖 Generated with Claude Code