> 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_28/session_15_documentation_validation_and_release.md). # Session 15: Documentation Validation And Release **Session ID**: `phase28-session15-documentation-validation-and-release` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Update the committed Trend Finder manuals and Reference mode registry to reflect the shipped Phase 28 behavior, preserve deferred source candidates and non-goals in durable docs, complete full validation and a security closeout, and delete the migrated `docs/ongoing-projects/trends-finderz.md` once coverage is confirmed. *** ## Source Mapping This closeout session has no new feature mapping; it discharges the documentation, validation, and safe-deletion obligations for the whole phase. The source file being retired is `docs/ongoing-projects/trends-finderz.md`; its full content (source URLs, deferred candidates, non-goals, do-not-regress areas, tier sequencing) is already folded into `.spec_system/PRD/phase_28/PRD_phase_28.md` and is reinforced in the current manuals below before deletion. *** ## Scope ### In Scope (MVP) * Update `docs/extensions/trend-finder-scoring.md` for dedup, per-signal quality, calibration version, confidence dampener, aging half-lives, refined saturation, lifecycle multiplier, and named contributions * Update `docs/extensions/trend-finder-pipeline.md` state table for the retention pass and dedup/coverage counters * Update `docs/extensions/trend-finder-ui-surfaces.md` (or the relevant manual) for visibility bands, suppressed-noise summary, action verdicts, Action Queue Brief section, pin baselines/notes/tags, search palette, KPI strip, and Markdown export * Update `docs/extensions/trend-finder-sources.md` for keyword packs, scan modes, rotation, coverage QA, and any direct adapters that landed * Refresh the Engine Replay Reference mode registry so committed Markdown matches shipped behavior (no planned-feature language) * Preserve deferred source candidates and explicit non-goals in durable docs (manuals + this PRD), not in a deleted planning file * Record a heading-by-heading coverage check for `docs/ongoing-projects/trends-finderz.md`: source material, method/caveats, items 1.1-10.4, where Trend Finder is already ahead, non-goals, and suggested sequencing all map to shipped docs, phase PRD sections, session specs, or explicit deferrals * Full validation: complete Vitest suite, Playwright e2e for new surfaces, payload-size budget check, private-artifact scan, and `bun audit` * Security closeout: confirm no new credential flow, runtime bridge, admin write, hosted storage, or unreviewed transfer path (Sessions 13-14 reviewed) * Delete `docs/ongoing-projects/trends-finderz.md` after a coverage check confirms every item is folded * Update `.spec_system/state.json` phase status and the master PRD ### Out of Scope * New feature work (all features ship in Sessions 01-14) * Re-deriving the mapping (it is already folded into the phase PRD) *** ## Prerequisites * [ ] Sessions 01-14 completed and validated *** ## Deliverables 1. Updated Trend Finder manuals and Reference mode registry reflecting shipped behavior 2. Durable record of deferred source candidates and non-goals in the manuals and PRD 3. Coverage-check artifact proving every trends-finderz heading/item has a durable destination before deletion 4. Full validation run (suite, e2e, payload budget, private-artifact scan, audit) with results recorded 5. Security closeout confirming no new threat surface beyond the compliance- reviewed Tier 4 changes 6. Deletion of `docs/ongoing-projects/trends-finderz.md` after coverage confirmation, plus state/PRD updates *** ## Success Criteria * [ ] Manuals and Reference mode track only shipped behavior; no planned-feature language remains * [ ] Deferred candidates and non-goals survive in durable docs after the planning file is deleted * [ ] The closeout records a heading-by-heading coverage check for every source section and item before deletion * [ ] Full suite, e2e, payload budget, private-artifact scan, and `bun audit` pass * [ ] Security review records no new unreviewed transfer or write path * [ ] `docs/ongoing-projects/trends-finderz.md` is deleted only after coverage is confirmed * [ ] `.spec_system/state.json` and the master PRD reflect Phase 28 completion --- # 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_28/session_15_documentation_validation_and_release.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.