[DEV-6506] Reshape Lazurio documentation for technical readers

[immakermatty]

Status

Ready for review.

Mission Control: mission-control/db/data/mission-control/plans/2026/08/DEV-6506-lazurio-public-documentation.yaml

Why

The product website and public documentation serve different audiences. The website can explain Lazurio at product level; this repository must give builders, technical evaluators, operators, and Task Agents one precise, source-backed explanation of how Lazurio currently works.

What changes

• reshapes the English navigation around a technical overview, quickstart, core concepts, an Example Organization, components/source, AI app workflows, operations, evaluation, and reference;
• adds the canonical glossary and separates people, agent roles, spaces, control surfaces, and Publication into distinct conceptual slices;
• documents a synthetic, public-safe Example Organization from provider identity and manifests through Workspace Modules and Launchpad, including a screenshot rendered from the real Launchpad UI with synthetic data;
• links Lazurio components and open-source foundations to public source while keeping the FSL license boundary explicit;
• adds truthful current workflows for Codex/ChatGPT Desktop, Claude, Cursor Glass/Agent Window, and Google Antigravity, including unavailable native-integration boundaries;
• updates all Lazurio evidence links to source revision 08d21803d4d4011304e1181ecf02ab9c5bfbad58 and expands the evidence map to 22 sources;
• keeps the same reviewed Markdown as the source for the human site, llms.txt, content-index.json, sitemap, and search;
• adds agent-retrieval, browser, accessibility, keyboard-scroll, and responsive coverage.

Deliberate non-goals

• no Knowledgebase content or authority changes;
• no publication of a live public Example Organization repository, which remains separately gated by DEV-6508;
• no Czech localization, Cloudflare production deployment, Dashboard implementation, or Lazurio MCP server;
• no claim that a side-by-side browser workflow is a native AI-app integration.

Verification

• bun run check — passed; 20 documents, 22 evidence sources, 0 Astro diagnostics, links/public-safety/agent-index passed;
• bun run build — passed; 20 documentation routes, Pagefind, sitemap, and / -> /en/ redirect verified;
• bun run test:browser — passed; 16 desktop/mobile Chromium tests including serious/critical Axe checks;
• bun /Users/matejsuchanek/Conglomerate/scripts/pr-preflight.mjs — passed at exact HEAD 706bafe19b3763038305d4c1853e8069f545b5df;
• visual QA completed in the Codex in-app browser for the technical homepage, Example Organization, embedded Launchpad screenshot, and AI app support matrix.

Risks and follow-up

Provider UI capabilities can change independently. Their source records carry review dates and the support matrix intentionally distinguishes current verified paths from future possibilities. Publication of this PR updates documentation only; production deployment remains an explicit follow-up.

Greptile Summary

This PR reorganizes Lazurio’s English documentation for technical readers and expands the source-backed material for setup, concepts, example organization structure, AI application workflows, operations, and reference.

• Adds a technical quickstart, canonical glossary, Example Organization, component inventory, and AI application guides.
• Restructures navigation around starting, building, AI applications, operations, evaluation, and reference.
• Adds keyboard-focus treatment for rendered code blocks and broadens browser and retrieval coverage.
• Updates Lazurio evidence links to a single pinned source revision and expands the evidence map.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete changed-code defect identified.

The new navigation targets correspond to added documents, the expanded metadata satisfies the repository’s validation contracts, and the accessibility behavior is covered by a browser assertion against rendered output.

Important Files Changed

Filename	Overview
app/v2/astro.config.mjs	Adds an Expressive Code post-processing plugin that makes rendered code blocks keyboard-focusable and gives them an accessible label.
data/v2/docs/en/quickstart.md	Adds the source-checkout setup path, Launchpad startup instructions, optional desktop and CLI installation, and Organization and Module checks.
data/v2/docs/en/example-organization.md	Documents a synthetic Organization’s identity, generated files, manifests, repository layout, Launchpad representation, and lifecycle commands.
data/v2/docs/en/use-with-ai-apps.md	Adds a support matrix that distinguishes in-app, side-by-side, and unavailable native integration paths across supported AI applications.
data/v2/docs/en/index.mdx	Replaces the IT-first landing page with a technical overview and directs builders toward the quickstart and Example Organization.
data/v2/sidebar.ts	Reorganizes all English documentation into technical start, organization building, AI application, operations, evaluation, and reference sections.
data/v2/source-map.json	Pins Lazurio evidence to the new reviewed revision and adds source records for CLI, Launchpad, schemas, lifecycle contracts, and AI application providers.
app/v2/tests/documentation.spec.ts	Updates the primary navigation test and adds coverage for the Example Organization, AI application limitations, accessibility, and focusable code blocks.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Technical overview] --> B[Quickstart]
    B --> C[Core concepts and glossary]
    C --> D[Example Organization]
    D --> E[Components and source]
    E --> F[AI app workflows]
    F --> G[Operations and security]
    G --> H[Evaluation and reference]
    I[Reviewed Markdown and MDX] --> J[Astro documentation site]
    I --> K[llms.txt]
    I --> L[content-index.json]
    I --> M[Sitemap and search]
    N[source-map.json] --> I

Loading

_{Reviews (1): Last reviewed commit: "Documentation: Add technical Lazurio gui..." | Re-trigger Greptile}

[immakermatty]

Tak myslím si, že bychom měli udělat follow-up pull request, který z tohoto pull requestu vytáhne části, které dávají smysl, eh, zachovat, a jinak zbytek zahodíme, jelikož dokumentace už se posunula i více produktovým směrem