> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_31/session_07_release_polish_and_documentation.md). # Session 07: Release Polish And Documentation **Session ID**: `phase31-session07-release-polish-and-documentation` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make the public demo credible, clear, responsive, and maintainable after the core path works. *** ## Scope ### In Scope (MVP) * Add visible frozen-snapshot provenance in the top bar or route headers. * Tune snapshot content so major surfaces are populated without implying live hosted collection. * Add polished empty or unavailable states for removed local actions. * Review mobile layout on key routes. * Run a bundle budget review against Pages output. * Add a direct-upload smoke command if the Pages project name is available. * Update `docs/deployment.md` with the Pages demo path after it is proven. * Record release closeout notes for public demo readiness. ### Out of Scope * Hosted collection or scraping. * Hosted scheduler. * Hosted local-agent control plane. * Secret-bearing runtime. * Account auth, OAuth, or API-key flows. * Raw local memory, transcript, prompt, command, or document publication. * Replacing the existing local-first AI OS runtime. * Migrating away from the existing Cloudflare Workers deployment path. * Adding analytics without separate privacy review. *** ## Folded Source Details Public demo interpretation rules: * Users must be able to tell the hosted site is a frozen public demo, not a live local runtime. * Trend Finder pages must identify data as a frozen demo snapshot, fixture/demo data, deterministic fallback, or redacted generated source snapshot. * Do not use "live" unless the source was genuinely live at capture time and is safe to describe that way. * Empty and unavailable states should explain that hosted actions are disabled, not broken. * The demo should show the complete product surface with realistic frozen data while making it clear no local collectors or machine reads are running. Content tuning targets: * Major host surfaces should be populated enough to demonstrate layout and scanning behavior. * Usage totals should be rounded or bounded. * Agent/session rows should be visibly fixture-backed. * Trend Finder can use public evidence, provenance labels, source health summaries, score breakdowns, creator angles, watchlist items, and Engine Replay stages only when the projection and source-compliance docs allow them. * AI Rogue should stay browser-local and not imply default enablement outside public demo mode. Documentation targets: * `demo-website/README.md` already covers Pages project settings from Session 05; this session verifies it after the path works. * `docs/deployment.md` gets a Pages demo section only after build, preview, smoke, and scan behavior are proven. * Documentation must explain Cloudflare Git deployment and direct upload, or record the missing Pages project name as the only direct-upload constraint. * Existing Workers deployment docs remain intact and separate. Release gates to record together: * `bun run demo:build:pages` * Static preview route matrix. * No `/__*` request assertion. * Fixture and generated-output privacy scans. * Typecheck and focused tests. * Bundle budget review against Pages output. * Mobile route review. * Direct upload result or documented external Pages project-name constraint. Deferred item: * A repo CI guard for Pages build plus secret/path scan is deferred until the demo stabilizes unless added earlier by an implementation decision. *** ## Prerequisites * [ ] Session 06 validates route coverage and privacy behavior. * [ ] Generated output exists for bundle review. * [ ] Pages project name is known if direct-upload smoke is expected. * [ ] Mobile route review targets are selected from the smoke route matrix. *** ## Deliverables 1. Clear public demo provenance and unavailable-state copy. 2. Mobile layout fixes for the route matrix. 3. Deployment documentation for the independent Pages demo flow. 4. Optional direct-upload smoke command or documentation that the project name must be supplied by the operator. 5. Release closeout notes for public demo readiness. 6. Bundle budget review result for Pages output. *** ## Success Criteria * [ ] Users can tell the hosted site is a frozen public demo, not a live local runtime. * [ ] Key routes are usable on desktop and mobile. * [ ] Documentation explains both Cloudflare Git deployment and direct upload, or records the missing Pages project name as the only direct-upload constraint. * [ ] Phase 31 release gates are recorded together before completion. * [ ] The public demo remains separate from the Worker deployment path. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_31/session_07_release_polish_and_documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.