Arena v11.0.2

Everything else

• A corpus is built once and read seven times, so the reference case stops rebuilding it per reference
• Every surface that states a version states 11.0.2, and server.json is one of them
• preparing release
• A search weighs where a word lands, and "badge" reaches ArenaBadge
• A served document links where this server answers, and not into a checkout
• A style hoisted into a constant is styling, and danger-fill reads it there
• A blurb is lifted whole, and stack.md stops publishing half of its own claim
• The catalogue cards land, and NOT_YET_REWRITTEN empties
• Both npm pages are written in the register, and one of them stopped repeating page.md
• Every component prompt is written in the register, and the family limit says why it moved
• Two hundred more prompt sentences carry one claim each
• Four hundred and twenty-eight prompt sentences, rewritten in the register
• A component description is consumer prose, and it is written like it
• The last three reference pages, and one stale count they were carrying
• The tree a project walks before its first screen reads one node at a time
• The style kernel is written in the register, and one table stops saying "the same"
• When the markup is yours, it is written in the register too
• The page you paint is written in the same register, and pays for itself
• The router is the first page written in the register the gate holds
• Every statement of a rule is one statement, and says what holds it

Every commit: v11.0.1...v11.0.2

Arena v11.0.1

Everything else

• Every surface that states a version states 11.0.1
• The release route pays for a version surface no gate on it reads
• The registry entry is sent by the run that published, or it drifts from the package
• A server.json the guard cannot see is an entry the registry never hears about
• A manifest the registry reads and nothing here holds goes stale in silence

Every commit: v11.0.0...v11.0.1

Arena v11.0.0

Everything else

• Every surface that states a version states 11.0.0
• Eight appearances of one component, which is what the benches already show
• The language travels in the server, and a component package is code

Every commit: v10.2.4...v11.0.0

Arena v10.2.4

Everything else

• Every surface that states a version states 10.2.4
• A branch that only a pull request may reach is not pushed to
• The page that describes how the site is published names the repository it builds
• A bench a reader can open is named by the address that opens it
• the workflow that publishes the site builds the products it publishes
• the environment table names the variable the site reads, and the route pays for it
• the site carries the products it draws, on the domain that makes the claim
• a pair carries the name a reader knows it by
• a property read with a fallback is a property that resolves
• the site carries every half it declares and declares every half it carries
• what the site publishes under web-benches is read from what it published
• A closed overlay names a part, and nothing it names is drawn
• A layer opened before the order is stated is the lowest of the document, not the highest
• The site's "See it" list ends where Arena is seen drawing something else
• Eight products Arena draws, named where a stranger reads before deciding
• The contract is the property, and being operable by an agent is what follows from it
• One sentence with three homes goes stale in two of them
• The breakpoint warning is a browser's diagnosis, and a server render never reaches it

Every commit: v10.2.3...v10.2.4

Arena v10.2.3

arena-to-prod

• nothing put Arena where an editor looks, so the command writes the one discovery record and reads it back

docs

• a command nobody is told about is one nobody runs, so both branches name the record and what reads it back

mcp

• Arena over the Model Context Protocol, as transport rather than a third copy of the language

packages

• the record a consumer gets was never held to the standard it claims, and the two things no gate here can reach are now written down
• the tarball shipped the components and none of the language, so it carries the corpus an agent reads and every path in it resolves where a consumer stands

skills

• the consumer branch documented bun as a requirement Arena does not have, so what it supports is stated with the evidence behind each answer

Everything else

• preparing minor release
• preparing release

Every commit: v10.2.2...v10.2.3

Arena v10.2.2

community

• a read spec excluded a gitignored directory that only exists on a developer machine, so check:graph failed everywhere it does not

focus trap

• the wait after a Tab read a snapshot that Tab had already moved, and asked a one-stop panel for a move it cannot make

gates

• three read specs named files their gate never opens, so the graph carried a dependency the run does not have

graph

• the audit called check:pixel-parity unfollowable, and the gate it renders the same pages as had been audited all along
• three gates read the fonts, colours and bundles they render without declaring them, so the cache kept them while their subject changed

target size

• the enhanced floor and the density arguing for it were the same claim in two places, and nothing failed when either moved

Everything else

• preparing minor release

Every commit: v10.2.1...v10.2.2

Arena v10.2.1

citations

• four names pointed at a page this repository forbids, and the gate cited as proving the rename complete reads .md alone

table and styles

• the recipe composed every slot from scratch on every call, and the grid counted every cell of every row to read two of them

Everything else

• preparing minor release

Every commit: v10.2.0...v10.2.1

Arena v10.2.0

affordances

• the closed set had no word for the one gesture a phone makes, and the seven components that answer a press declared nothing

api

• "identical members, idiomatic binding" answered a platform that spells a member differently and said nothing about one that cannot spell it

behaviour

• the role a pattern requires was legible only through a scripts constant, which is the one file a contracts package cannot carry

browser gates

• an expression that threw came back as an empty value, and a six second run reported two pages as having waited forty seconds

contracts

• the three levels a platform target is told to read left this repository by no route at all

contrast

• prefers-contrast and forced-colors returned zero matches in the whole repository, so the one accessibility setting Arena answered was motion

packaging

• the manifest built an identity and a runtime in one function, so a package with no Node would have inherited a command it cannot run

press

• seven components drew a state a phone never shows and none for the gesture a phone actually makes

publish

• the contracts package was assembled, gated and packed, and had no way to leave the machine

release notes

• a release page was written from the push of the tag, so it announced a tree no run on main had gated

safe area

• the rule that a pinned component pays its own inset was true of four components and held by nothing
• the rule said Arena drew nothing that needed the insets while four components drew them, and the bar under the notch paid none

target size

• twelve parts missed the floor WCAG asks at its minimum, comfortable left most of them exactly where they were, and nothing measured any of it

tokens

• a dimension said what it measures and never what the reader asking for larger text does to it, which is the one thing a phone must know and cannot derive

workflows

• the page said two workflows publish a package, the directory held three, and the cache list it enumerated named neither the third nor its tree

Everything else

• preparing minor release

Every commit: v10.1.2...v10.2.0

Arena v10.1.2

hero

• a design system with no picture of itself, in front of an audience that asks for one first

packages

• the engine floor refused the Node line the framework it ships for accepts

seo

• every index page and the 404 handed a search engine another page as the one to keep

Everything else

• preparing release

Every commit: v10.1.1...v10.1.2

Arena v10.1.1

ci

• a pull request into develop ran no gate at all, and the one workflow that would now have run on it billed three operating systems per revision of every contribution

contributing

• the policy refused every external pull request, seven documents repeated the refusal, and a gate asserted the sentence so it could not be edited in one place

publish

• the guard that decides whether a package changed read no path at all, and git reads no path as every path

Everything else

• preparing release

Every commit: v10.1.0...v10.1.1