oficina / sheets Public

Shared primitives go to oficina/estilo, not rastrillo/ui

Paul's ruling, confirmed directly rather than on either of the two
relays that reported it: the design system stays rastrillo's, and the
CARLOS suite gets its own variant. An inspector panel shared by a
document editor and a spreadsheet is the suite's component, not the
framework's. Repo created the same day.

The distinction that produced the correction is worth more than the
outcome: two callers at design time is the bar for extraction, and says
nothing about destination. Both consuming sessions were told to propose
to the library and applied the right bar to the wrong question, because
the first answer looked like it settled the second. It will recur for
every piece either app hands upward, so it is recorded rather than left
in a message thread.

Creating estilo now rather than building app-local first, because two
consumers already exist at design time — the extraction bar is met, not
pending, and building locally would guarantee merging two
implementations later, which is the outcome the bar exists to prevent. I
had recommended the opposite to ui-guidelines-52 an hour ago, applying
one-consumer logic to a two-consumer situation; docs-e6 caught it.

The colour engine is unaffected and stays in ui: Pair and allocation are
contrast arithmetic against floors the framework already gates, so they
are a function rather than a component, and both apps call the same one
wherever their components live.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01APtNStXDZ5H2fAc1ZuGqtS