Bradley/stackbench test - #5766
Draft
bradleyshep wants to merge 467 commits into
Draft
bradleyshep wants to merge 467 commits into
bradleyshep wants to merge 467 commits into
Conversation
Contributor
There was a problem hiding this comment.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
bradleyshep
force-pushed
the
bradley/stackbench-test
branch
from
August 31, 2026 17:38
6a1eb7d to
dc1a416
Compare
bradleyshep
force-pushed
the
bradley/stackbench-test
branch
from
September 7, 2026 20:22
32d3018 to
837c1f7
Compare
The only 105a mutations duplicated 1e and 4b defects and survived, since 105a signs in fresh after a restart rather than reloading. Each stack now loses the account's cart across that restart or fresh sign-in instead.
The setup's add-to-cart write was still in flight when the offline cut closed every connection, so the Keyboard line was sometimes never committed and the reconnect check failed without an app defect. The setup now waits for the server-pushed cart line first.
…tions 622b now expects the named product before opening it, so an unpublished name fails both catalog checks at an observation and the mutation targets both. 1d first confirms the signed-out view holds before reloading, because a reference app that reloads itself on signout collided with the harness reload.
Listing plans compiled all 98 saved plans on the HTTP thread, about 15 minutes per pass on the appliance; plans are now cached by path, size and modification time and discovered in the reader worker. Live cost read each transcript whole every five seconds; it now reads only new bytes.
Reference, full mutation and null-control evidence from controller image 3213109: every stack scores 176/176 on its reference, every mutation is caught at its target assertion (convex 142, mongodb 157, postgres 166, spacetime 154), and the empty app earns nothing. qualification status reports the calibration ready with no blockers.
Admission held the 9.25 GiB sum of every container cap for each attempt's first minute. Across 29 attempts of the four-stack L3 qualification, whole attempts peaked at 1.9 GiB in their first minute and 3.1 GiB overall, so admission now holds 2.5 GiB. The caps themselves are unchanged.
A Windows checkout with autocrlf stores the same commit with CRLF, so every scope hash differed from the appliance's and recorded evidence looked stale locally. The scope now hashes text as Git stores it (LF), which leaves every LF-tree hash unchanged.
Only admission's startup memory reservation and the scope hash's line endings changed since the evidence was recorded; no grading code did. The reviewed decision pins each scope's old and new executable hash.
The action registry gained repeatFormWrite without a representative step, so the runtime-contract and fixture-coverage tests failed.
The backend sidecar holds each stack's database and peaked at 922 MiB of its 1 GiB cap during qualification, so a spike could kill a correct database and charge the failure to the stack. The appliance guide's cap totals are corrected, and the reviewed reuse decision covers the change.
…end as unknown The broker refused server tools, MCP servers, containers, fast speed and priority tiers, and on OpenAI hosted tools, files, stored prompts and server-side conversations, only because its token rates could not price them. That changed what the agent could do. It now forwards them and counts each as unpriced: receipts stay reconciled, reports show the spend as at least its priced part, and an attempt cost cap no longer promises budget to a retry after unpriced spend. The reviewed L3 reuse decision covers the change; qualification uses the model-free reference agent, which sends no provider requests.
…ication Adding a stack no longer changes any existing stack's qualification scope: - shared code names no stack; per-stack behaviour sits behind adapter fields in src/stacks/backends/<stack>-*.ts, and stack modules may not import another stack's modules - qualification scope ownership is by filename, registries are hashed per stack, and src/stacks/backends/<stack>/ holds each stack's runtime assets - contract interface blocks are excluded from the recipe meaning hash and bound to their own stack's scope Supabase runs as seven services in the attempt's network namespace behind its firewall: database, auth, data API, realtime, storage, edge functions and a gateway without admin routes. Data-level reset keeps a realtime canary in the publication. Named operations are PostgreSQL functions called through the data API. Includes the L1-L3 native reference, guidance, contract interface blocks and grading support.
The recipe meaning hashes moved because meaning now covers interface-neutral contract text; execution hashes are unchanged. The reviewed reuse carries the existing postgres, mongodb, spacetime, convex and null evidence to the new executable scopes without reruns.
146 known-defect controls against the Supabase reference, covering every scored L1-L3 check. Manifests are checked against the registered stack ids. Live qualification has not run yet.
…dence scopes - The cross-origin probe measures an application that blocks the response with CORP; the stored write still decides the check. - Appliance admission skips a run whose ports Docker cannot publish and stops on any other Docker error. - The L3 calibration's evidence must cover exactly each stack's reference and mutation scopes plus the null control, however many targeted reruns it has. Each new case fails when its fix is removed.
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
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.
Description of Changes
This PR adds Stack Bench, a reproducible benchmark for coding agents building applications against SpacetimeDB, PostgreSQL, and MongoDB.
Benchmark definitions and grading
passed,failed,inconclusive, orharness_failure.Ecommerce benchmark
Runs, repairs, and campaigns
CLI, dashboard, and appliance
SpacetimeDB TypeScript SDK
TableReffrom an anonymous readonly type alias to a readonly interface with the same members.TableRefis used incorrectly.ConnectionManagerreconnects to reuse the identity token previously issued by the server.TableRefdiagnostics.SpacetimeDB CLI
spacetime devto retain configuration changes made during direct-login publishing.SpacetimeDB skills
API and ABI breaking changes
This PR changes the public Rust signature of:
spacetimedb_cli::publish::exec_from_entryThe function now accepts
&mut Configinstead of takingConfigby value. External Rust callers must pass a mutable reference. The API-breaking label should be applied unless the previous entry point is preserved through a compatibility wrapper.The exported TypeScript
TableRefdeclaration changes from a type alias to an interface while retaining the same readonly member contract.Automatic TypeScript client reconnection also changes behavior by presenting the identity token from the previous successful connection.
Expected complexity level and risk
3 / 5
Most of the implementation is isolated under
tools/stack-bench. The principal risks are benchmark correctness, evidence integrity, concurrent resource isolation, interrupted-run recovery, Docker cleanup, and credential handling.The TypeScript reconnect change and
spacetimedb-clihelper signature are the only changes outside the benchmark and skill directories.Testing
TableRefregression tests: 4/4 passed.cargo check -p spacetimedb-cli.exec_from_entryRust signature.