> 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_40/session_18_full_validation_and_handoff.md).

# Session 18: Full Validation And Handoff

**Session ID**: `phase40-session18-full-validation-and-handoff` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Prove the port is complete, safe, and documented before the work is considered ready to merge.

***

## Scope

### In Scope (MVP)

* Run focused bridge, hook, parser, chat, Ministry, voice, and control-plane guard tests added by earlier sessions.
* Run broad validation commands: typechecks, full tests, lint, asset checks, private-data scan, and build/demo scans where UI or public output changed.
* Manually smoke live mode, demo mode, model selection, MoA presets, context meter, commands, compact, Ministry, MoA save, voice respawn, and redaction.
* Verify no generated private data, raw local paths, auth JSON paths, account material, logs, coverage, or secret-shaped strings are staged.
* Record pass/fail results, root causes for failures, and bounded follow-up if a validation item cannot be completed.

### Out of Scope

* Starting new feature work.
* Leaving intentionally unported upstream behavior implicit.
* Treating failed validation as complete without root cause and follow-up.

***

## Prerequisites

* [ ] Sessions 01 through 17 are complete.

***

## Deliverables

1. Final validation log or implementation summary.
2. Manual smoke checklist results.
3. Handoff notes for any bounded follow-up.

***

## Success Criteria

* [ ] Required validation commands pass, or failures are documented with root cause and bounded follow-up.
* [ ] Completion criteria in the folded Phase 40 source record are satisfied or explicitly scoped out with rationale.
* [ ] No private/generated data or secret-shaped strings are committed.

***

## Folded Source Session Split

The section below preserves the original Phase 40 session split detail for this session, including dependencies, decisions, outputs, and acceptance checks.

### Session 18: Full Validation And Handoff

**Objective**: Prove the port is complete, safe, and documented before the work is considered ready to merge.

**Scope**:

* Run focused bridge, hook, parser, chat, Ministry, voice, and control-plane guard tests added by earlier sessions.
* Run broad validation commands: typechecks, full tests, lint, asset checks, private-data scan, and build/demo scans where UI or public output changed.
* Manually smoke live mode, demo mode, model selection, MoA presets, context meter, commands, compact, Ministry, MoA save, voice respawn, and redaction.
* Verify no generated private data, raw local paths, auth JSON paths, account material, logs, coverage, or secret-shaped strings are staged.
* Record pass/fail results, root causes for failures, and bounded follow-up if a validation item cannot be completed.

**Outputs**:

* Final validation log or implementation summary.
* Manual smoke checklist results.
* Handoff notes for any bounded follow-up.

**Dependencies / Notes**:

* Depends on Sessions 01 through 17.
* If a feature is intentionally not ported, validate the not-ported rationale and docs rather than leaving it implicit.

**Acceptance Checks**:

* Required validation commands pass, or failures are documented with root cause and bounded follow-up.
* Completion criteria in this document are either satisfied or explicitly scoped out with rationale.
* No private/generated data or secret-shaped strings are committed.


---

# 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_40/session_18_full_validation_and_handoff.md?ask=<question>&goal=<endgoal>
```

`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.