resources/license.mdx still names the end-user surface "Console" twice — the page was outside #79's 48-file sweep #107

Found while executing #101 (the four authored-prose in-fence lines). Filed rather than folded in: #101's scope is exactly three files, and this is a fourth.

What is there

Two occurrences on content/docs/resources/license.mdx, neither inside a code fence:

license.mdx is not among the 48 files PR #100 changed, so these two were never graded against #79's three categories — they were missed by the sweep, not kept by it. A grep for the retired name over the English corpus after #101 lands returns these two plus four deliberate keeps (see below).

Why it needs a call rather than a mechanical rewrite

Both occurrences sit in a licence-scope enumeration — a list of the artifacts covered by Apache-2.0. That is arguably the "a thing the product ships" category #79 deliberately left alone (its commit message names "a plugin id (Console UI), a line the CLI prints, a box in an architecture diagram"), and line 95 pairs it with "Account UIs", a name #79 kept everywhere.

Against that: #79's outcome is that the end-user surface has no name. A licence that grants rights over "the Console" names a thing the rest of the corpus no longer calls anything, which is a worse failure mode in a licence than in a diagram — a reader checking what is Apache-2.0 cannot map "Console" onto a surface the docs never mention.

So the question is narrow: does a licence-scope enumeration name shipped components (exempt, like a plugin id) or the end-user surface (rename)? Line 95's "the Console and Account UIs" reads like component names; line 16's bare "Console" between "production runtime" and "the MCP server" reads like the surface.

Possible outcomes:

• Rewrite both to whatever the licence should call the surface, matching Retire "Console" as the name of the end-user surface; keep a name only for the admin surface (Setup) #79's landed vocabulary (the UI, or ObjectOS where a destination is meant).
• Keep both as component names, and say so somewhere so the next grep does not reopen this.
• Split the two: line 95 is a component list, line 16 is the surface.

Nobody is misled about their rights either way — the artifacts are the same artifacts. This is vocabulary, same class as #101.

Deliberate keeps, for whoever grades this

These four are not part of this card — they are the "thing the product ships" category #79 kept on purpose, and I confirmed each:

• why.mdx:79 — "Console (basic)" describes Supabase's admin UI in a comparison table, not ours.
• architecture.mdx:16 and configure/system-settings.mdx:19 — "Console UI" as a plugin id / architecture box.
• quickstart.mdx — genuine os start banner output, owned by quickstart.mdx sample os start output does not match what CLI 17.0.0 prints, and the plugin count is wrong #94.

Checked for duplicates first: no open issue covers license.mdx. #102 records a different #79 coverage gap (the name Studio) and does not reach this page.

Related: #79, #101, #102.

Generated by Claude Code