v1.1.0

Changelog

• a8567ae Give first boots ten minutes in the session-start hook, and close the second-round doc gaps
• 5fa1912 Finish the remaining simulation findings for 1.1.0
• d8dacb2 Re-run setup on every --rebuild, and document where setup must install
• 72eaf8f Fix the four release blockers the setup simulations found
• 562f11b Keep the two config keys 1.0 accepted loading, as the 1.0 contract requires
• e6872f1 Parse pkg/boxer file by file in its docs test; ParseDir is deprecated
• 6f1c382 Test that every CLI flag, config key and Go API is in its reference page
• 7467892 Stamp the test's egress denial during the command, not just before it
• 4f53796 Frame boxer as a sandbox per workstream, as a microVM or a container
• 92c676e Cut copy that says nothing or talks down to the reader
• cf3ddd5 Give every kind of reader a path into the docs
• 4de93ac Merge boxer's hooks into .codex/hooks.json and .dsh/hooks.json instead of overwriting them
• 22d0e32 Make the case for boxer on the homepage, README and intro
• 79f6534 Explain the automatic path: install once, and every worktree gets its own sandbox
• b44fd79 Give the watch test's cleanup a write to fail on
• 725f867 Reorganise the docs around how a developer adopts boxer, and rewrite them plainly
• 4945cfe Test that watch stops in both output forms when every write fails
• b60e268 End boxer watch when its reader goes away
• 96fe049 Raise the internal/vm coverage floor to 65 now that the Apple driver is tested everywhere
• 77c9b7e Stop the container drivers racing on a shared output buffer
• e5f12e0 Build the docs in CI the way Pages does, and cover the Apple driver without its runtime
• 8b1c633 Record that the Pages workflow's action pins were checked against their tags
• ea6f24c Add a motivation section to the README
• 4f85170 Re-measure the benchmarks on the current build, and test the page against the data
• 34ca729 Resolve the contradictions the docs review left open
• b26fd2a Document boxer for release, and fix what reviewing the docs found
• 28d502a Run boxer on every backend on Linux, and fix what that and the open items found
• 936824e Review the docs as a newcomer would, and fix what that found
• 575b4e0 Run boxer on Linux, fix what that found, and trace the inside-cell flake to a real bug
• 7bd6933 Sweep the docs, rebuild the site around four backends, and add runnable examples
• 183f11a Add four backends, portless URLs, a management CLI, and the evidence for them
• ed8def6 Build the docs site in CI
• 7fec247 Give the user documentation one home instead of two
• 83a5ec2 Split what had grown too big, and write the documentation as a site
• 817addb Support fx, and make the scorecard demanding enough to be worth reading
• 4290ecf Score every claim a cell makes, and widen the matrix to every level
• b2ba220 Record the matrix at full coverage, and show the pane when a prompt hangs
• 98b7cd8 Sandbox the shell a launcher starts, and the worktree a launcher makes
• 93625a8 Add an eval tier that varies the integration level, not the task
• 76e1ed0 Report what each agent actually did, not just whether it passed
• 4b423b9 Record a clean sweep: twelve development lifecycles, all passing
• 28eadab Give each worktree its own port, and finish the lifecycle findings
• 93d6c7b Report twelve development lifecycles and what they found
• c60ee36 Explain an out-of-memory kill, and the forwarded-port origin trap
• a0b496f Add an SDLC tier: can somebody actually develop in one of these?
• 490c09d Prove the agent uses a sandboxed MCP server, and fix what stopped it
• 360045e Split what a pack can cache from what it must not (1.1 Stream A, corrected)
• 54c119b Record the 1.1 gate: T1 68/0/1, smoke 53/53
• b27d17e Mention the devcontainer in the README's configuration section
• 001f0d9 Tell the README how to see what is running and what it costs
• f4a407b Copilot's inside mode is run, not merely listed
• 2e536a9 Put the flow tier in the release gate
• 35c4d69 Put [env] where TOML means it, after the scalar keys
• eab707c Repair a stranded comment in the requirements
• ec247e4 List 1.1's configuration keys in the requirements
• 379cb3e Finish Stream D: resources on status, events in the watch stream
• 514c141 Test the environment cache's drop path and the flow tier's own helpers
• 02627c2 Finish Stream A: a cache you can drop, and one that stays bounded
• e026e65 Record the Copilot guest fix in the status report and changelog
• a3f7572 Make the Copilot inside cell actually work
• 386207f Put an agent in the flow session
• 848d4ef Make the Conductor verification a ten-minute procedure
• 5b9c58f Mark the flow tier done: it passes
• b3c3ae9 Close the Stream G items and record what remains
• 1e02b51 Document the MCP server that runs in the sandbox
• b40e035 Record the flow tier's first passing run
• cc75fa3 Run the Copilot inside cell instead of claiming it
• 9527b83 Show what the service printed when readiness times out
• a81b5e2 Add the flow tier: one development session, end to end (1.1 Stream F)
• 0933f5d Read the devcontainer a repository already has (1.1 Stream C)
• 75d233c Make the core answerable by a user interface (1.1 Stream D)
• 2ae85ce Let a project say what it needs to run (1.1 Stream B)
• b6705f8 Cache the environment, not just the image (1.1 Stream A)
• 50a1fad Rewrite the 1.1 plan as the plan of record
• 19b9779 Plan a flow tier: one real development session, end to end
• b079685 Open no registry for an image that is never pulled
• dfa72fa Propose the 1.1 plan: a development environment, not just a command sandbox
• b06aa12 Say which Conductor settings keys are documented and which are a guess
• b2cedc5 Test what a user meets first: installing, and being in the wrong place