Docs: Align the Launchpad and Buddy glossary entries with the Lazurio shell

[immakermatty]

Why

The Lazurio shell decisions change how two basic glossary terms read for users. The glossary still called the Launchpad "Lazurio's home screen, where you choose an Organization" and did not say where Buddy appears. Since this PR was first written, root decision 0185 (2026-10-04) and the evening addendum to 0179 (2026-10-03) changed the shell again:

• Launchpad becomes Apps in the switch Chat · Apps · Automate, with two sections: Workspace (every module the Environment's GitHub identity reaches) and Productionspace (production repositories, read-only). No grouping by Team. The Organization section of the first target is gone.
• The rail switches spaces (the personal space and one GitHub avatar per Organization), not Environments. The Environment is chosen in the picker at the top of the left column, with the Settings gear beside it.
• Buddy is Buddy: on the person's behalf he coordinates their Agents with the same authority over them as the person; he is neither an Agent nor an app. He runs in the person's personal Remote Environment and appears as a floating chat at the bottom right of every screen (decision 0180).

What changes

data/v2/docs/{en,cs}/guide/glossary.md:

• Launchpad: the overview of your Organization's applications in your Environment, where you open or start one. Today you choose an Organization in it and modules are grouped by Organization. In the upcoming version it is called Apps in the switch and shows two sections, Workspace and Productionspace (read-only), without grouping by Team; you choose the Environment in the picker at the top of the left column, with the Settings gear beside it, while the rail switches between your personal space and your Organizations.
• Buddy: Buddy is Buddy; on your behalf he coordinates your Agents and has the same authority over them as you; neither an Agent nor an app; beyond that he represents you only within the scope you allow. He runs in your personal Remote Environment; in the upcoming version you talk to him in a floating chat at the bottom right of every screen.
• Czech: the Launchpad entry no longer calls the Environment "prostředí" (decision 0170).
• updatedAt and reviewedAt move to 2026-10-04 in both locales (the validator requires reviewedAt to cover the update). Review owner Anna Blazickova and second reviewer Pablo AI confirm the facts by reviewing this head.

data/v2/source-map.json: lazurio-platform-shell-target is re-pinned from LazurioPlatform 8e86e4a (first target, three sections, rail of Environments) to fd9b0f0133758f305e5becae8539cfee9f919967, whose "Target shell" section records the second iteration (decision 0185) and the two-section Apps home. Reviewed 2026-10-04, due 2027-01-04 (the three-month window used for Lazurio sources).

Both entries keep the "upcoming version" / "připravovaná podoba" framing: the shell is decided and built only as a prerelease, and AGENTS.md requires separating current implementation from target.

What does not change

• No other glossary entries. Older wording elsewhere in the glossary (Principal, AI Colleague, Machine, "pracovní prostředí" for Lazurio itself) is outside this PR.
• Buddy is not described as an "Operator": the Operator is always a person; Buddy holds the same authority over Agents as that person.
• No Microsoft source is touched here; the expired Microsoft sources are fixed separately in Docs: Re-review the five Microsoft Copilot sources (fixes #28) #30.

Verified

On head b1c9f07 (fast-forward on top of the approved d459ce1; the branch already sat on current main 4b73e2e, so the rebase was a no-op):

• cd app/v2 && bun run check → exit 1, failing only in validate:content on the five Microsoft sources that expired on 2026-09-26 (Content check fails on main: five Microsoft Copilot evidence sources expired on 2026-09-26 #28):
  Evidence source microsoft-copilot-architecture expired on 2026-09-26 (and the same line for -data-protection, -privacy, -requirements, -extensibility).
• The remaining steps run one by one on this head: locale parity 30/30, astro check 0 errors / 0 warnings / 0 hints, Checked links in 36 documents., Public-safety scan passed for 46 source files., agent index 6/6, deployment/source-gate/smoke/brand tests 39/39.
• This head merged with Docs: Re-review the five Microsoft Copilot sources (fixes #28) #30 (the Content check fails on main: five Microsoft Copilot evidence sources expired on 2026-09-26 #28 fix) in a throwaway worktree: bun run check → exit 0, Validated 36 documents and 21 evidence sources.
• git diff --check clean; Lazurio root scripts/pr-preflight.mjs → ready_to_push.
• Rendered locally with astro dev; /en/guide/glossary/ and /cs/guide/glossary/ checked in Chrome via Playwright (200, both entries render as intended).

Follow-ups

• CI test stays red here until Docs: Re-review the five Microsoft Copilot sources (fixes #28) #30 is merged; after that, rebase this branch on main and request an exact-head re-review. Pablo's approval was for d459ce1; this head changes the text, so it needs a new review.

🤖 Generated with Claude Code

Confidence Score: 4/5

The PR appears safe to merge, though the glossary would benefit from clearer current-versus-planned wording and evidence for the new shell details.

Findings

1.  Current and planned Launchpad blur ▶
2.  New shell claims lack evidence ▶

Summary

Updates the English and Czech glossary entries for Launchpad and Buddy to describe the planned shell, and advances both pages’ update and review dates.

• The current Launchpad definition needs a clearer boundary from the upcoming interface.
• The new shell details need traceable evidence or clearer provisional framing.

_{Reviews (1) · Last reviewed commit: "Docs: Align the Launchpad and Buddy glos..."}

[agentrozjedemeai]

Reviewed exact head fa5d752. The two unresolved content findings are real for this trust-critical public glossary. In both locales, the rail-switch sentence is present tense despite that UI being explicitly upcoming; distinguish the current Organization selection from the future Apps home throughout the definition. More importantly, the new 0179/0180 shell and Buddy claims still have only sourceRefs lazurio-readme, lazurio-architecture and lazurio-collaboration-model, all pinned to the 2026-08-27 root revision in data/v2/source-map.json; add a current public reviewed decision/source reference for these claims and retain the current-vs-target wording. Focused locale-parity tests pass (30/30), but Verify/test fails on the five pre-existing Microsoft source expirations (#28). Do not bypass that required red check; after content corrections and evidence renewal, request exact-head rereview before merge.

[agentrozjedemeai]

@immakermatty — APPROVED for content on exact head d459ce1. Both locales now separate current Organization selection from the future Apps home, three sections and rail. Source map pins the reviewed public Platform #138 merge 8e86e4a9a25a613f7baf1e11401b1ea68ab74bbd, whose Target shell is marked not implemented. Locale parity 30/30, latest diff --check clean and addressed threads resolved. Do NOT merge: Verify/test remains red; local validate:content independently fails on exactly five expired Microsoft source records (#28). Renew and rerun required checks first; no bypass.

[agentrozjedemeai]

APPROVED — exact head b1c9f07. Re-reviewed the changed English/Czech Launchpad and Buddy entries against decision 0185 and the immutable LazurioPlatform fd9b0f0 source: upcoming Apps has Workspace and Productionspace, the Environment picker and adjacent settings gear sit in the column head, rail switches spaces, and Buddy runs in the personal Remote Environment. The current/target distinction remains explicit. DELIVERY HOLD: this head has a red test because the five Microsoft sources expire on current main. It merges cleanly after #30, but must be updated from main and pass fresh CI; after a new head, obtain a new exact-head review. Production GA4 owner readback remains a separate release gate. No unresolved threads.