0.2.0

Added

• Version numbers. This changelog marks each release, the release notes on GitHub are built from it, and the site's footer shows the version. (#30)
• The first time the checks appear, one line says what they are: what green, red, amber and a dash mean, and that nothing has touched your files yet. (#29)
• The landing page shows the benchmark's numbers, read from the benchmark itself, and links every case. (#29)
• A changelog, here and at /changelog. (#28)
• Plan first switch in Composer, on by default and remembered per browser, in place of the Plan / Build / Iterate buttons. Turn it off to have Composer edit straight away; nothing is applied until you Apply either way. (#27)
• A fix now starts from the evidence. When a check is red, the agent gets every new issue, a failing test's message with its stack mapped to your files and lines, and the code here it broke, not only one line. (#24)
• Script errors in the live preview point to the line of your script file that threw, and every Composer turn is told about them. (#24)
• A Security page: the threat model, the sandboxes, what the checks cannot catch, and how to report a vulnerability. (#26)
• Background runs. Send a task and keep working. Each runs on its own copy, is checked, gets one automatic fix if a check is red, and waits on the agent board for you to open it. Your edits made meanwhile are merged in. (#23)
• Hooks. .aperture/hooks.json runs project scripts on save and as a check on every staged change. (#22)
• Rules for some files. .aperture/rules/\*.md with files: globs reach Composer only when a turn touches a matching file. (#22)
• A public benchmark of how often the checks stop a bad edit, with every case listed, misses included. (#21)
• The Types check runs the real TypeScript compiler, in a worker in your tab, across files. (#20)
• A model on your own computer (Ollama, LM Studio) from the hosted site; the agent loop runs in your tab. (#19)
• Editable plans: reword, reorder, remove or add steps before Build it. (#18)
• Check problems in the editor margin, with F7 to move between them. (#18)
• An agent board (Ctrl/Cmd+J) with every run by stage, and side-by-side compare of two staged runs. (#18)
• Pull requests driven to green: the status bar watches CI, and a failure can be sent to Composer with its annotations and log. (#18)
• Light and follow-system themes. (#17)
• Privacy and Terms pages, and account deletion in Settings. (#5, #6)
• Cmd/Ctrl-click a relative import to open that file. (#12)
• A diff review in one short pass: a note is kept only for a likely bug, and can be posted on the pull request. (#3)
• Parse, imports and types run inside the agent's own turn, so a red check gets one more step before the turn ends. (#4)

Changed

• The site and README say what Types is now: the TypeScript compiler, not a light check. The model section mentions a model on your own computer. (#29)
• On a phone, a first visit opens Composer and its demo tasks instead of a file. (#29)
• Touch screens start with the comfortable density. (#29)
• Signed out, the editor shows two sign-in links instead of three identical ones: the header's, and "Sign in to send" in Composer. (#29)
• The editor loads less up front: the zip library loads when you download. (#29)
• Composer's lessons (.aperture/lessons.md) stay out of what is sent to GitHub unless you tick them in, and never ride along with a CI fix. (#27)
• Privacy and Security are separate pages, and Privacy states plainly what passes through the server after sign-in. (#26)
• The landing page no longer downloads the editor, and every server input is checked against a schema. (#17)
• An edit is staged only when the agent is sure of it (confidence 0.8 or more), and Apply stays off while any check is red or still running. (#10, #12)
• A check fails only for problems the change brought in; problems the file already had show amber and do not block Apply. (#14)
• The README and the site describe all five checks, and say what Types does. (#8)
• No shared Grok key: the demo plays recorded runs, and everywhere else uses your own key. (#9)
• A demo GIF and video at the top of the README. (#11, #16)
• The site leads with the checks, and the demo shows no prices. (#1)
• A send uses the key saved on your account, and stops if it is missing. (#4)

Fixed

• Someone could sign up with another person's email and a password, and when that person later signed in with Google or X they landed in that account. A sign-in now joins an existing account only if its email was confirmed; otherwise the sign-in page says why and nothing is joined. (#30)
• Signed out on a phone, the top bar no longer runs off the edge of the screen; Pricing is in the footer there. (#30)
• Background jobs on Pro could stall once the server had answered. They are now kept alive, and a job the server ended says so instead of showing "running" forever. (#27)
• After a send to GitHub, only what was sent is recorded as in the repository. (#27)
• A check replaced by a newer change could still finish and show its old result, such as type errors in the margin from an earlier change. (#25)
• A stopped background run could come back as ready, and one restored after a reload never aged out. (#25)
• Preview errors could point at the wrong line after a stylesheet changed. (#25)
• The GitHub token is no longer kept in the browser's storage. (#17)
• An agent endpoint can no longer reach the server's own network, and every user-supplied endpoint is pinned to the address that was checked. (#7, #13)
• Revert refuses instead of discarding edits made after the commit. (#15)
• The light checks no longer misread ordinary code, and three GitHub round-trip bugs are fixed. (#14)
• The demo's recap no longer lists finished steps as left. (#13)
• The sign-in error log no longer records part of the session cookie. (#6)
• A custom model endpoint no longer follows redirects, so it cannot bounce your key to another address. (#2)