Repository navigation
docs: clarify shared-agent positioning and refresh product media - #1999
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
added 6 commits
October 1, 2026 20:10
added 10 commits
October 1, 2026 22:49
added 10 commits
October 2, 2026 01:17
Move the quick start directly under the demo and name the installer's default login. Bring back the seven-function operating-system table, the "why it exists" thesis, the full comparison list, the desktop app, the contributor notes and the Vstorm OSS ecosystem table. Drop the demo disclaimer, repeated budget and "depends on" caveats, the run-detail placeholder, the MEDIA production comments and the decorative window frame; the caveats stay in the governance and security pages. Answer the harness and Claude Code FAQ questions concretely. All four languages retranslated and restamped.
Describe the demo in one sentence so it reads without playing, end the first task in Activity where the run already shows its cost, and give developers the run endpoint as a copyable curl. Drop the repeated MCP count, the channel paragraph and the "see the work" paragraph that restated the gallery and the OS table.
Replace the sharing question, which restated the team section, with the on-premises one: local models and embeddings through Ollama or vLLM, PDFs through PyMuPDF or self-hosted LiteParse, nothing leaving unless a setting names a destination.
The page at /presentation/ is now the 44-slide guided introduction: every product screen shown whole, its parts numbered, then a zoom to each part, with an agenda, chapters, the organisation model, architecture and how a first project starts. index.html carries styles and script; screenshots and fonts sit beside it, each under 1 MB, and the 37-second recording plays from the README's existing upload. README and its translations link to it from the header and under the introduction, as does the combined README proposal.
GitHub Pages serves main, so until this merges the site's /presentation/ is still the old deck. The combined proposal's Guided tour link renders the new deck straight from this branch instead; the root README keeps the Pages address it will have after the merge. The deck also records its step in an absolute URL, which a previewer's <base> no longer breaks.
Keep the Sovereign Agentic AI Layer label as an eyebrow, restore the commit-access thesis from the current README, name pydantic-ai-harness, add the HIPAA configuration profile and a Community section, point the guided tour at the docs site and drop an unreferenced asset.
DEENUU1
force-pushed
the
codex/readme-product-tour
branch
from
October 5, 2026 09:34
50e14ec to
5aa6818
Compare
The combined variant from readmes/ replaces README.md, with every path rewritten for the repository root. The thirteen graphics it shows move to docs/assets/readme/ beside their attribution notes; the other proposals, their index and the unused graphics are removed with the readmes/ folder. The hero shows the desktop app's icon instead of Amigo, who now walks beside the desktop-app sentence. The Polish, German and Spanish READMEs are retranslated from the new text and record its fingerprint.
The README's headings open on an emoji, so GitHub answers "Quick start" with -quick-start. The assertion had been changed to quick-start, which no heading produces, and failed against the current README.
…ion/tour/ /presentation/ now serves a short open-source introduction: the problem, the thesis, code defines and configuration composes, the builder, files and code, knowledge with a cited answer, the eight surfaces, what the platform refuses, budgets, approvals and the run record, the two sovereignty setups, the stack with the load-test result and its conditions, today's limits, and how to start. The 44-slide product tour moves to /presentation/tour/ and shares the introduction's media/ and fonts/. It drops the "still being tried out" framing, the release-count tile and the "Earlier build" captions. The README "New here?" line and nav link describe the introduction and point to the tour, in all four languages, and llms.txt lists both decks.
The target pointed at the removed deck-build skill and printed the deck to a PDF expecting 20 pages. Both decks are now guided decks that show one slide at a time, so printing yields one page. The target now checks each deck's slide count (14 and 44) and runs the content-deck toolkit's asset check on both pages. A PDF of every step is built from a deck's source with guided.py --pdf.
docs/howto/translate.md keeps "run" and "vault" as product nouns, inflected (run, runa; vault, vaulcie), as the Polish docs pages already do. The README said "wykonanie" and "sejf". The run-tracking heading's anchor moves with it.
Drop the desktop icon from the heading and give the category label its own line under the name in all four languages; licence and engine move to a small line under the promise.
Move the recorded run and the screen gallery straight under the hero, and the quick start before the integrations section, in all four languages; the See it link leads the navigation.
…arm white Headings and large figures move to Instrument Serif, text and small headings to DM Sans, labels to DM Mono (all OFL, licences in fonts/OFL.txt). The beige palette becomes warm white with neutral hairlines and shadows. Inter, Geist Mono and Bricolage Grotesque are no longer used by the decks and are removed.
The intro (4K, narrated with a synthetic voice, captions burned in) comes first; the recorded planner run stays below it. Same change in all four READMEs, with a poster from the film's end card.
…tations What runs where gets each technology's mark (Pydantic, FastAPI, Next.js, Prefect, Redis, PostgreSQL, Docker); the 27 model providers, the sync sources and "Ollama or vLLM" get theirs. Marks come from the console's brand glyphs (Simple Icons CC0, Lobe Icons MIT) and Simple Icons 16.34; Heroku and LiteLLM have no published mark and get a neutral dot.
… from text The deck and its presenter window now accept messages only from each other on the same origin and send to that origin only; presenter notes and the slide list are built with textContent instead of innerHTML. Resolves the CodeQL client-side XSS, DOM-text-as-HTML and postMessage origin alerts on both decks.
… fix exists braces <= 3.0.3 (CVE-2026-93687) has no patched release, so neither raising a range nor an override can clear it. It arrives only through eslint-config-next > @next/eslint-plugin-next > fast-glob > micromatch, a lint-time dependency the built console does not ship. The Makefile names the advisory, its path and the condition that removes the exception; every other finding still fails.
Merged
DEENUU1
added a commit
that referenced
this pull request
Oct 5, 2026
### Summary Release 0.0.517: version, lock and changelog. ### Changes - `backend/pyproject.toml`, `frontend/package.json` and `backend/uv.lock` move to 0.0.517. - `CHANGELOG.md`: the `[Unreleased]` block becomes `[0.0.517] - 2026-10-05`, with a fresh empty `[Unreleased]` above it. - Ships #1999 and #2010: - a new README in four languages, with the 45-second intro film and a product tour in light and dark; - two presentations on the documentation site: the 14-slide introduction at `/presentation/` and the 44-slide tour at `/presentation/tour/`, restyled, with stack and provider marks; - the presenter view sends and accepts messages only from the page's own origin, and writes notes and the slide list as text; - `make audit-frontend` skips GHSA-vfj7-8cjw-p6xm (braces, no patched release, lint-time only).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Position AgenticOS as a self-hosted workspace where teams build, maintain and use shared AI agents. Retain Vstorm's required Sovereign Agentic AI Layer label in every README hero and explain sovereignty as control over deployment, models, data flows and access.
Show the product immediately with the agent builder, then a linked task overview, Quick start and the recorded example before the longer product tour. Localized section links let readers jump directly to the capability they need. The expanded tour covers:
Keep English, Polish, German and Spanish aligned. All README documentation links lead to the published site in the matching language. Update the maintainer positioning brief and capture inventory.
Media
Earlier commits also correct MCP approval documentation and add Outlook setup pointers in all four documentation languages. Pre-existing screenshot placeholders in the documentation and presentation remain outside this README refresh.
Validation
git diff --checkpass.Documentation and media changes only. Meridian was created in a fresh live agent run and checked in the browser; its figures are fictional demonstration data. No fresh installation, external provider connection, directory sign-in or full video playback was performed for this capture revision. Existing test-deployment results illustrate the interface, not production performance.