v1.1.2

What's Changed

• The evaluation's API key read from a file only its owner reads by @rafaelmatosdasilva in #186
• A name an object inherits is no colour and no easing curve by @rafaelmatosdasilva in #188
• The package leaves out the release archive the workflow writes beside it by @rafaelmatosdasilva in #187

Full Changelog: v1.1.1...v1.1.2

v1.1.1

What's Changed

• Scorecard can also be run on demand by @rafaelmatosdasilva in #182
• Each release also on npmjs.org, with provenance, through trusted publishing by @rafaelmatosdasilva in #184
• The skill evaluation runs through the Agent SDK on an API key by @rafaelmatosdasilva in #185

Full Changelog: v1.1.0...v1.1.1

v1.1.0

What's Changed

• How to contribute, and the workflows' actions on their Node 24 versions by @rafaelmatosdasilva in #176
• A page with drafts waiting still gets its other gaps drafted by @rafaelmatosdasilva in #175
• Test tools on their patched versions, with the one advisory that has no fix recorded and why by @rafaelmatosdasilva in #177
• Each release also published as a package on GitHub Packages by @rafaelmatosdasilva in #178
• A Figma read is sent to the team's snapshots store at once by @rafaelmatosdasilva in #180
• Property tests with fast-check for the value readers every comparison rests on by @rafaelmatosdasilva in #179
• The Nuxt advisory OSV matches through an open-ended range, recorded with why by @rafaelmatosdasilva in #181

Full Changelog: v1.0.0...v1.1.0

v1.0.0

What's Changed

• Style guide: theme fonts embedded, steadier sticky heads, buttons sized by the page by @rafaelmatosdasilva in #1
• Style guide: personality, Identity layout, module data, stricter private check by @rafaelmatosdasilva in #2
• Accessibility keys and screen-reader names, the iconography lenses, contracts and Code Connect by @rafaelmatosdasilva in #3
• Fix main's failing tests; clearer Parity rows by @rafaelmatosdasilva in #4
• Status: the Parity card counts only built components by @rafaelmatosdasilva in #5
• Intent layer page: the For column says what a page is for by @rafaelmatosdasilva in #6
• Intent layer: content check, fixes made in the layer, drafts and review, proposals; Identity icons; Changelog by release by @rafaelmatosdasilva in #7
• Style guide tabs: 1px smaller by @rafaelmatosdasilva in #8
• Accessibility try in the build: never waits for a person by @rafaelmatosdasilva in #9
• Where each part lives, one token per person, saved accessibility results, Documentation page by @rafaelmatosdasilva in #10
• Escaped class selectors, the agent's command line in evaluations, the same request the same page by @rafaelmatosdasilva in #11
• Publishing the style guide sends the page and what it links to, never the rest of its folder by @rafaelmatosdasilva in #12
• Documentation page statuses, Status cards, open tasks' age, who decided, downloads in a viewer by @rafaelmatosdasilva in #13
• Kept differences: a part of their own, and a rule agents follow by @rafaelmatosdasilva in #14
• Profile run from inside the code's GitLab copy by @rafaelmatosdasilva in #16
• The team's themes in a store of their own, shared by each style guide build by @rafaelmatosdasilva in #15
• GitLab links found where the project is now; the Documentation page says Done by @rafaelmatosdasilva in #17
• Intent layer: what a page lacks written from the code or drafted for review, sent in parts; one status a row on the Documentation page by @rafaelmatosdasilva in #18
• Identity in dark mode: both personality readings, and the icon's construction line, read by @rafaelmatosdasilva in #19
• A Documentation page for every system; notes no agent reads flagged Remove by @rafaelmatosdasilva in #20
• Documentation page with no intent layer: columns under their own headings by @rafaelmatosdasilva in #21
• Intent layer reader: titled lines kept once, drafts in prose sections stay drafts by @rafaelmatosdasilva in #23
• Documentation page: columns line up again, every row dated by @rafaelmatosdasilva in #22
• Prototype catalog: what the request needs, the code's own props, and where a component goes by @rafaelmatosdasilva in #24
• Prototypes as pages in the system's own code, held to the system; what agents invent fed back to the documentation by @rafaelmatosdasilva in #25
• The documentation under load: what agents cannot learn, which component they cannot tell apart, and a sweep of real pages by @rafaelmatosdasilva in #26
• Every test closes the documentation gaps it can: the code's facts written as final, the rest drafted for review by @rafaelmatosdasilva in #27
• --ci-changed: a scheduled pipeline builds only when something it is made from moved by @rafaelmatosdasilva in #28
• Panels open with what to do (What and Where); a fresh GitLab connection after a long wait by @rafaelmatosdasilva in #29
• Intent layer: every answer does its own work, each with a command to copy by @rafaelmatosdasilva in #30
• A page written from a shared spec gets one of its own; the company command is always installed by @rafaelmatosdasilva in #31
• Accessibility per theme by @rafaelmatosdasilva in #32
• Private check: more of the people and companies the work drew on by @rafaelmatosdasilva in #33
• The default theme is called the default one; plain-word project names are watched in context by @rafaelmatosdasilva in #34
• Each repository the setup names says what is there: the engine writes its README on every run by @rafaelmatosdasilva in #36
• Browser tests read the same on any computer by @rafaelmatosdasilva in #37
• A place's own write token, with a fallback for computers without it by @rafaelmatosdasilva in #38
• A TypeScript that cannot read JSX is no TypeScript; headless Chrome starts in light by @rafaelmatosdasilva in #35
• The words of the web are nobody's secret by @rafaelmatosdasilva in #39
• Prototypes ask before they guess, and are reviewed as pages in any framework by @rafaelmatosdasilva in #41
• Stores: read without a token of your own, and say whose run wrote by @rafaelmatosdasilva in #40
• The style guide links its styles, code, fonts and data as files beside it by @rafaelmatosdasilva in #42
• A reloaded style guide opens at its top; publishing removes the last build's files by @rafaelmatosdasilva in #43
• Mirrors can live in a cache on this computer, and audit.mjs can be searched by @rafaelmatosdasilva in #45
• A store can live on GitHub; a run stopped at a limit is recorded apart by @rafaelmatosdasilva in #44
• A page says which components it wrote without reading their card by @rafaelmatosdasilva in #47
• Built around the same component twice over is a piece it does not have by @rafaelmatosdasilva in #48
• A job that would publish the style guide's page alone is named and stopped by @rafaelmatosdasilva in #46
• A system with no intent layer can finish its documentation by @rafaelmatosdasilva in #49
• The documentation table's columns spread across its width by @rafaelmatosdasilva in #50
• A static component's role is read from its code; developers' notes in the code are never to remove by @rafaelmatosdasilva in #54
• Coverage asks the questions agents actually get stuck on by @rafaelmatosdasilva in #51
• A check that cries wolf is named, and never silenced by @rafaelmatosdasilva in #52
• The style guide's files go in an assets folder beside the page by @rafaelmatosdasilva in #53
• The engine says when the style guide the team opens is behind, and can publish it itself by @rafaelmatosdasilva in #55
• Every page the engine opens works at full speed, each in a window of its own by @rafaelmatosdasilva in #56
• A store's README stops flipping between runs; a commit that landed despite a 502 is sent by @rafaelmatosdasilva in https://github.com/rafaelmatosdasilva...