# purmemo-mcp - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for purmemo-mcp. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0003` supported 0.86
- **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `src/codex/SKILL.md` Claim: `clm_0004` supported 0.86

## What It Can Do

- **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `src/codex/SKILL.md` Claim: `clm_0001` supported 0.86
- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## How to Start

- `curl -fsSL https://app.purmemo.ai/install | sh` Evidence: `README.md` Claim: `clm_0005` supported 0.86
- `npm install -g purmemo-mcp && purmemo` Evidence: `README.md` Claim: `clm_0006` supported 0.86
- `npx purmemo-mcp@latest init` Evidence: `README.md` Claim: `clm_0007` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Needs admin / security approval
- **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first.

### 30-Second Read

- **What to do now**: Needs admin / security approval
- **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing
- **Do not trust yet**: Tool permission boundaries cannot be trusted before install.
- **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86
- **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `src/codex/SKILL.md` Claim: `clm_0004` supported 0.86
- **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `src/codex/SKILL.md` Claim: `clm_0001` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0005` supported 0.86

### What You Cannot Trust Yet

- **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `CLAUDE.md`, `src/codex/SKILL.md`
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md`

### What Continuing Will Touch

- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `CLAUDE.md`, `src/codex/SKILL.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `ARCHITECTURE.md`, `CONTRIBUTING.md`, `README.md`, `SECURITY.md` et al.
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0008` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0009` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `src/codex/SKILL.md` Claim: `clm_0001` supported 0.86
- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0002` supported 0.86

### Context Scale

- Total files: 200
- Important-file coverage: 40/200
- Evidence index entries: 79
- Role / Skill entries: 1

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for purmemo-mcp, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat purmemo-mcp as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for purmemo-mcp, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 1 role / Skill / project-doc entries.

- **purmemo** (skill): Persistent AI conversation memory. Recall context at session start, save progress at session end. Essential for project continuity across sessions. Activation hint: When the user's task is highly relevant to the workflow described by “purmemo”, use it for a pre-install experience first, then decide whether to install. Evidence: `src/codex/SKILL.md`

## Evidence Index

- Indexed 79 evidence entries.

- **Purmemo Workflow System** (documentation): Comprehensive workflow automation for Claude Code powered by MCP tools Purmemo, Krawlr, Context7, Render, Supabase . Evidence: `.claude/README.md`
- **Purmemo Project Instructions** (documentation): Session Startup: Get Project Context Evidence: `CLAUDE.md`
- **pūrmemo** (documentation): ! npm version https://badge.fury.io/js/purmemo-mcp.svg https://www.npmjs.com/package/purmemo-mcp ! npm downloads https://img.shields.io/npm/dm/purmemo-mcp.svg https://www.npmjs.com/package/purmemo-mcp ! Tests https://github.com/purmemo-ai/purmemo-mcp/actions/workflows/test.yml/badge.svg https://github.com/purmemo-ai/purmemo-mcp/actions/workflows/test.yml ! License: MIT https://img.shields.io/badge/License-MIT-yellow.svg https://opensource.org/licenses/MIT Evidence: `README.md`
- **purmemo-ios** (documentation): Native iOS app for Purmemo — save memories, recall context, and inject AI context from anywhere on your iPhone. Evidence: `purmemo-ios/README.md`
- **ADR-033 — Purmemo Documentation Repository Architecture** (documentation): ADR-033 — Purmemo Documentation Repository Architecture Evidence: `docs/adr/ADR-033-documentation-repository-architecture.md`
- **ADR-037: CLI Hook Platform-Adapter Architecture** (documentation): ADR-037: CLI Hook Platform-Adapter Architecture Evidence: `docs/adr/ADR-037-cli-hook-platform-adapter-architecture.md`
- **Package** (package_manifest): { "name": "purmemo-mcp", "version": "15.7.24", "mcpName": "io.github.purmemo-ai/purmemo", "description": "MCP server for pūrmemo - AI conversation memory that works everywhere. Save and recall conversations across Claude Desktop, Cursor, and other MCP-compatible platforms. Intelligent context extraction, smart titles, living documents.", "main": "dist/server.js", "type": "module", "bin": { "purmemo": "./dist/server.js", "purmemo-mcp": "./dist/server.js", "purmemo-mcp-setup": "./dist/setup.js", "purmemo-mcp-hooks": "./dist/setup.js" }, "files": "dist/", "src/commands/", "src/gemini/", "src/codex/", "src/remote/widgets/", "src/remote/login.html", "src/remote/success.html", "src/remote/icon.pn… Evidence: `package.json`
- **Contributing to Purmemo MCP** (documentation): Thank you for your interest in contributing to Purmemo MCP! This document provides guidelines for contributions. Evidence: `CONTRIBUTING.md`
- **Package** (package_manifest): { "name": "purmemo-desktop", "version": "1.0.0", "description": "Purmemo Desktop — always-on memory presence for macOS", "main": "dist/main.js", "scripts": { "start": "electron .", "dev": "tsc --watch & electron .", "build:ts": "tsc", "build": "npm run build:ts && electron-builder --mac", "build:win": "npm run build:ts && electron-builder --win", "build:linux": "npm run build:ts && electron-builder --linux", "pack": "npm run build:ts && electron-builder --dir" }, "keywords": "purmemo", "memory", "electron", "desktop" , "author": "Purmemo ", "license": "MIT", "devDependencies": { "@types/better-sqlite3": "^7.6.13", "@types/node": "^20.0.0", "electron": "^28.0.0", "electron-builder": "^24.0.0… Evidence: `_retired/purmemo-desktop/package.json`
- **Package** (package_manifest): { "name": "purmemo-mcp", "version": "12.9.0", "description": "MCP server for pūrmemo - AI conversation memory that works everywhere. Save and recall conversations across Claude Desktop, Cursor, and other MCP-compatible platforms. Intelligent context extraction, smart titles, living documents.", "main": "src/server.js", "type": "module", "bin": { "purmemo-mcp": "./src/server.js", "purmemo-mcp-setup": "./src/setup.js", "purmemo-mcp-hooks": "./src/setup.js" }, "files": "src/", "README.md", "LICENSE" , "scripts": { "start": "node src/server.js", "setup": "node src/setup.js setup", "status": "node src/setup.js status", "logout": "node src/setup.js logout", "hooks": "node src/setup.js hooks", "te… Evidence: `bundle/server/package.json`
- **Purmemo Memory Skill** (skill_instruction): You have access to purmemo MCP tools for persistent memory across sessions. Evidence: `src/codex/SKILL.md`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE`
- **Architecture** (documentation): This document describes the architecture of purmemo-mcp, an MCP server for cross-platform AI conversation memory. Evidence: `ARCHITECTURE.md`
- **Environment Setup Guide** (documentation): 2. Fill in your tokens in .env already done if you're the maintainer Evidence: `docs/ENVIRONMENT_SETUP.md`
- **ADR-009: Part Intelligence Propagation — Index → Parts Taxonomy Sync** (documentation): ADR-009: Part Intelligence Propagation — Index → Parts Taxonomy Sync Evidence: `docs/adr/ADR-009-part-intelligence-propagation.md`
- **ADR-011: macOS Distribution Strategy for Purmemo Desktop App** (documentation): ADR-011: macOS Distribution Strategy for Purmemo Desktop App Evidence: `docs/adr/ADR-011-desktop-macos-distribution.md`
- **ADR-016: Recency-Hybrid Recall Retrieval — Temporal Query Awareness** (documentation): ADR-016: Recency-Hybrid Recall Retrieval — Temporal Query Awareness Evidence: `docs/adr/ADR-016-recency-hybrid-recall-retrieval.md`
- **ADR-017: MCP Distribution Parity Strategy** (documentation): ADR-017: MCP Distribution Parity Strategy Evidence: `docs/adr/ADR-017-mcp-distribution-parity.md`
- **ADR-027: Reranker Optimization Per Surface** (documentation): ADR-027: Reranker Optimization Per Surface Evidence: `docs/adr/ADR-027-reranker-optimization-per-surface.md`
- **ADR-031: CLI Device-Authorization Flow & Identity Binding** (documentation): ADR-031: CLI Device-Authorization Flow & Identity Binding Evidence: `docs/adr/ADR-031-api-key-leak-prevention-and-identity-binding.md`
- **ADR-032: Artifact Replacement Primitives — Promote, Snapshot, Commit, Render** (documentation): ADR-032: Artifact Replacement Primitives — Promote, Snapshot, Commit, Render Evidence: `docs/adr/ADR-032-artifact-replacement-primitives.md`
- **ADR-039: Encryption Key Derivation — Persisted Random Key Supersedes Hostname-Derived Key** (documentation): ADR-039: Encryption Key Derivation — Persisted Random Key Supersedes Hostname-Derived Key Evidence: `docs/adr/ADR-039-encryption-key-derivation.md`
- **purmemo installer — one-line install for Windows.** (source_file): purmemo installer — one-line install for Windows. Usage: irm https://app.purmemo.ai/install.ps1 iex Or inspect first recommended for the security-conscious : irm https://app.purmemo.ai/install.ps1 -OutFile install.ps1 notepad install.ps1 .\install.ps1 What this does: 1. Checks for Node.js = 18. 2. If Node is missing, points you at the official installer. 3. Runs npm i -g purmemo-mcp to install the CLI. 4. Verifies purmemo is on your PATH and prints next steps. Source: https://github.com/purmemo-ai/purmemo-mcp/blob/main/scripts/install.ps1 Evidence: `scripts/install.ps1`
- **--- step 1: detect Node -----------------------------------------------------** (source_file): set -eu NODE MIN MAJOR=18 PKG="purmemo-mcp" BIN="purmemo" if -t 1 && -z "${NO COLOR:-}" ; then BOLD="$ printf '\033 1m' " DIM="$ printf '\033 2m' " GREEN="$ printf '\033 32m' " YELLOW="$ printf '\033 33m' " RED="$ printf '\033 31m' " RESET="$ printf '\033 0m' " else BOLD="" DIM="" GREEN="" YELLOW="" RED="" RESET="" fi say { printf '%s\n' "$ "; } step { printf '%s→%s %s\n' "$BOLD" "$RESET" "$ "; } ok { printf '%s✓%s %s\n' "$GREEN" "$RESET" "$ "; } warn { printf '%s!%s %s\n' "$YELLOW" "$RESET" "$ "; } die { printf '%s✗%s %s\n' "$RED" "$RESET" "$ " &2; exit 1; } say "" say "${BOLD}purmemo installer${RESET}" say "${DIM}AI memory + workflows for Claude. https://purmemo.ai${RESET}" say "" --- ste… Evidence: `scripts/install.sh`
- **Intelligent Memory** (source_file): import type { IntelligentContext, ProgressIndicators, Relationships, ClusteringHints, Methodology } from './types.js'; ⋮---- function extractProjectContext content: string : IntelligentContext ⋮---- // ============================================================================ // 1. PROJECT NAME DETECTION // ============================================================================ ⋮---- // Pattern 1: File paths highest priority // e.g., /Users/username/projects/myproject/v1-mvp/frontend/... ⋮---- // Pattern 2: Explicit project mentions // e.g., "in the Purmemo project", "working on FutureShift" ⋮---- // Pattern 3: Package.json or project config files ⋮---- // Pattern 4: Domain/URL refer… Evidence: `src/intelligent-memory.ts`
- **Server** (source_file): import { Server } from '@modelcontextprotocol/sdk/server/index.js'; import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'; ⋮---- import { SSEServerTransport } from '@modelcontextprotocol/sdk/server/sse.js'; import { CallToolRequestSchema, ListToolsRequestSchema, ListResourcesRequestSchema, ReadResourceRequestSchema, ListPromptsRequestSchema, GetPromptRequestSchema } from '@modelcontextprotocol/sdk/types.js'; import { extractProjectContext, generateIntelligentTitle, extractProgressIndicators, extractRelationships } from './intelligent-memory.js'; import TokenStore from './auth/token-store.js'; import { detectInstallMethod } from './auth/install-detection.js'; impor… Evidence: `src/server.ts`
- **Types** (source_file): export interface ToolAnnotations { title: string; readOnlyHint: boolean; destructiveHint: boolean; idempotentHint: boolean; openWorldHint: boolean; } ⋮---- export interface ToolMeta { 'openai/outputTemplate'?: string; 'openai/toolInvocation/invoking'?: string; 'openai/toolInvocation/invoked'?: string; 'openai/widgetAccessible'?: boolean; 'openai/widgetDomain'?: string; key: string : string boolean undefined; } ⋮---- export interface MCPTool { name: string; annotations: ToolAnnotations; meta?: ToolMeta; description: string; inputSchema: Record ; } ⋮---- export interface MCPResource { uri: string; name: string; description: string; mimeType: string; meta?: Record ; } ⋮---- export interface MC… Evidence: `src/types.ts`
- **Purmemoapp** (source_file): struct PurmemoApp: App { @State private var authService = AuthService private var screenshotManager = ScreenshotManager.shared ⋮---- var body: some Scene { ⋮---- private var mainTabView: some View { Evidence: `purmemo-ios/purmemo-ios/PurmemoApp.swift`
- **Authservice** (source_file): struct LoginRequest: Codable { let email: String let password: String ⋮---- struct LoginResponse: Codable { let access token: String let refresh token: String let token type: String ⋮---- struct RefreshRequest: Codable { ⋮---- var isAuthenticated = false var userEmail: String = "" var oauthError: String? ⋮---- let callbackURL = "\ Self.oauthCallbackScheme ://oauth callback" ⋮---- let loginURL = URL string: "\ baseURL /api/v1/oauth/\ provider /login?return url=\ encoded " else { ⋮---- let session = ASWebAuthenticationSession ⋮---- private func handleOAuthCallback callbackUrl: URL?, error: Error? { ⋮---- let email = await self.fetchUserEmail token: token ⋮---- private func fetchUserEmail toke… Evidence: `purmemo-ios/purmemo-ios/Services/AuthService.swift`
- **Keychainservice** (source_file): enum KeychainKey: String { ⋮---- struct KeychainService { ⋮---- private static let accessGroup = "DC7489SG7F.ai.purmemo.shared" ⋮---- static func save value: String, for key: KeychainKey { ⋮---- let query: CFString: Any = ⋮---- static func load key: KeychainKey - String? { ⋮---- var result: AnyObject? let status = SecItemCopyMatching query as CFDictionary, &result ⋮---- static func delete key: KeychainKey { ⋮---- static func deleteAll { Evidence: `purmemo-ios/purmemo-ios/Services/KeychainService.swift`
- **Purmemoapi** (source_file): class PurmemoAPI { private let baseURL = "https://api.purmemo.ai" private let authService: AuthService ⋮---- init authService: AuthService { ⋮---- func saveMemory content: String async throws - SaveMemoryResponse { let token = try await authService.validToken let url = URL string: "\ baseURL /api/v1/memories/" ! var request = URLRequest url: url ⋮---- let body = "content": content, "source type": "mobile ios" ⋮---- let newToken = try await authService.refreshToken ⋮---- func saveScreenshotMemory imageData: Data, context: String async throws - SaveMemoryResponse { ⋮---- let jpeg = UIImage data: imageData ?.jpegData compressionQuality: 0.5 ?? imageData let base64 = jpeg.base64EncodedString ⋮-… Evidence: `purmemo-ios/purmemo-ios/Services/PurmemoAPI.swift`
- **Purmemoapp** (source_file): struct PurmemoApp: App { @State private var authService = AuthService private var screenshotManager = ScreenshotManager.shared ⋮---- var body: some Scene { ⋮---- private var mainTabView: some View { Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/PurmemoApp.swift`
- **Keychainservice** (source_file): enum KeychainKey: String { ⋮---- struct KeychainService { private static let accessGroup = "DC7489SG7F.ai.purmemo.shared" ⋮---- static func save value: String, for key: KeychainKey { ⋮---- let query: CFString: Any = ⋮---- static func load key: KeychainKey - String? { ⋮---- var result: AnyObject? let status = SecItemCopyMatching query as CFDictionary, &result ⋮---- static func delete key: KeychainKey { Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/PurmemoMessages/KeychainService.swift`
- **Keychainservice** (source_file): enum KeychainKey: String { ⋮---- struct KeychainService { ⋮---- private static let accessGroup = "DC7489SG7F.ai.purmemo.shared" ⋮---- static func save value: String, for key: KeychainKey { ⋮---- let query: CFString: Any = ⋮---- static func load key: KeychainKey - String? { ⋮---- var result: AnyObject? let status = SecItemCopyMatching query as CFDictionary, &result ⋮---- static func delete key: KeychainKey { ⋮---- static func deleteAll { Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/PurmemoShare/KeychainService.swift`
- **Authservice** (source_file): struct LoginRequest: Codable { let email: String let password: String ⋮---- struct LoginResponse: Codable { let access token: String let refresh token: String let token type: String ⋮---- struct RefreshRequest: Codable { ⋮---- class AuthService { var isAuthenticated = false var userEmail: String = "" var oauthError: String? ⋮---- private let baseURL = "https: ⋮---- private static var activeAuthSession: ASWebAuthenticationSession? ⋮---- init { ⋮---- /// Explicit deinit avoids Swift runtime crash with SWIFT DEFAULT ACTOR ISOLATION=MainActor /// on iOS String { let url = URL string: "\ baseURL /api/v1/auth/me" ! ⋮---- func refreshToken async throws - String { ⋮---- let url = URL string: "\ bas… Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/Services/AuthService.swift`
- **Claudechannelstream** (source_file): private let logger = Logger subsystem: "ai.purmemo.purmemo-ios", category: "SSE" ⋮---- class ClaudeChannelStream { private var task: Task ? private var authService: AuthService private var retryDelay: TimeInterval = 1 private let maxRetryDelay: TimeInterval = 30 private set var isConnected = false ⋮---- var onMessagesLoaded: ClaudeChannelMessage - Void ? var onMessageReceived: ClaudeChannelMessage - Void ? var onMessageDeleted: String - Void ? ⋮---- init authService: AuthService { ⋮---- func connect { ⋮---- func disconnect { ⋮---- private func streamLoop async { ⋮---- private func openStream async throws { let token = try await authService.validToken ⋮---- let url = URL string: "https://api… Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/Services/ClaudeChannelStream.swift`
- **Keychainservice** (source_file): enum KeychainKey: String { ⋮---- struct KeychainService { ⋮---- private static let accessGroup = "DC7489SG7F.ai.purmemo.shared" ⋮---- static func save value: String, for key: KeychainKey { ⋮---- let query: CFString: Any = ⋮---- static func load key: KeychainKey - String? { ⋮---- var result: AnyObject? let status = SecItemCopyMatching query as CFDictionary, &result ⋮---- static func delete key: KeychainKey { ⋮---- static func deleteAll { Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/Services/KeychainService.swift`
- **Purmemoapi** (source_file): class PurmemoAPI { private let baseURL = "https://api.purmemo.ai" private let authService: AuthService ⋮---- init authService: AuthService { ⋮---- func saveMemory content: String async throws - SaveMemoryResponse { let token = try await authService.validToken let url = URL string: "\ baseURL /api/v1/memories/" ! var request = URLRequest url: url ⋮---- let body = "content": content, "source type": "mobile ios" ⋮---- let newToken = try await authService.refreshToken ⋮---- func saveScreenshotMemory imageData: Data, context: String async throws - SaveMemoryResponse { ⋮---- let jpeg = UIImage data: imageData ?.jpegData compressionQuality: 0.5 ?? imageData let base64 = jpeg.base64EncodedString ⋮-… Evidence: `purmemo-ios/purmemo-ios/purmemo-ios/Services/PurmemoAPI.swift`
- **Oauth Manager** (source_file): import express from 'express'; import open from 'open'; import { execFile } from 'child process'; ⋮---- import TokenStore from './token-store.js'; import type { TokenData } from '../types.js'; import type { Server } from 'http'; ⋮---- function escapeHtml str: string : string ⋮---- interface OAuthConfig { apiUrl?: string; clientId?: string; redirectUri?: string; } ⋮---- class OAuthManager ⋮---- constructor config: OAuthConfig = ⋮---- // Removed complex browser opening strategies - going manual-first // The performOAuthFlow method now handles everything clearly ⋮---- / Get current authentication token @returns {Promise } Access token or null if not authenticated / async getToken ⋮---- // Firs… Evidence: `src/auth/oauth-manager.ts`
- **Token Store** (source_file): import { existsSync, readFileSync, writeFileSync, chmodSync, mkdirSync } from 'node:fs'; ⋮---- import type { TokenData, UserInfo, EncryptedPayload } from '../types.js'; import { getActiveTokenFile, getConfigDir } from './profile-resolver.js'; ⋮---- function loadOrCreatePersistedKey configDir: string : Buffer ⋮---- function deriveLegacyKey : Buffer ⋮---- class TokenStore ⋮---- constructor tokenFile?: string ⋮---- async ensureConfigDir : Promise ⋮---- encrypt data: TokenData : EncryptedPayload ⋮---- decrypt encryptedData: EncryptedPayload : TokenData ⋮---- async saveToken tokenData: TokenData : Promise ⋮---- async getToken : Promise ⋮---- async clearToken : Promise ⋮---- async hasToken : Prom… Evidence: `src/auth/token-store.ts`
- **Universal Auth** (source_file): import { execFile } from 'child process'; import { promisify } from 'util'; ⋮---- interface AuthOptions { client?: string; purpose?: string; interactive?: boolean; } ⋮---- class UniversalAuthManager ⋮---- constructor ⋮---- async authenticate options: AuthOptions = ⋮---- // Check for existing valid token ⋮---- // Show authentication options ⋮---- async webLoginFlow client ⋮---- // Try to open browser ⋮---- // SECURITY: Use execFile no shell to prevent command injection via URL ⋮---- async apiKeyFlow ⋮---- / Create new account flow / async createAccountFlow ⋮---- // Call registration API ⋮---- async importFromClient ⋮---- async manualTokenEntry ⋮---- / Non-interactive authentication for scrip… Evidence: `src/auth/universal-auth.ts`
- **Purmemo First Message** (source_file): import { dbg, errLog, readState, writeState, loadApiKey, apiGet, readHookInput, detectPlatform, initPlatformPaths, platformEvent, } from './purmemo lib.js'; ⋮---- function countUserMessages transcriptPath: string : number ⋮---- async function main : Promise Evidence: `src/hooks/purmemo_first_message.ts`
- **Api Client** (source_file): import { structuredLog } from './logger.js'; import { AsyncLocalStorage } from 'node:async hooks'; ⋮---- let resolveApiKey = ⋮---- export function setRequestApiKey key: string null export function clearRequestApiKey ⋮---- export function runWithApiKey key: string, fn: = Promise : Promise ⋮---- export function initApiClient ⋮---- // ============================================================================ // Circuit Breaker Pattern // ============================================================================ ⋮---- export class CircuitBreaker ⋮---- constructor name, failureThreshold = 5, recoveryTimeout = 60000 ⋮---- async execute fn ⋮---- onSuccess ⋮---- onFailure error ⋮---- getStatus… Evidence: `src/lib/api-client.ts`
- **Logger** (source_file): export function logStructured level, message, context = Evidence: `src/lib/logger.ts`
- **Refresh Token Store** (source_file): import { createCipheriv, createDecipheriv, createHash, randomBytes } from "node:crypto"; ⋮---- export function hashApiKey apiKey: string : string ⋮---- function encrypt plaintext: string : string ⋮---- function decrypt envelope: string : string null ⋮---- export async function saveRefreshToken apiKey: string, refreshToken: string, expiresAtMs: number = Date.now + 90 24 60 60 1000, : Promise ⋮---- export async function loadRefreshToken apiKey: string : Promise ⋮---- export async function deleteRefreshToken apiKey: string : Promise Evidence: `src/remote/refresh-token-store.ts`
- **Handlers** (source_file): import { structuredLog } from '../lib/logger.js'; import { makeApiCall, sanitizeUnicode, safeErrorMessage, wafSafeBody } from '../lib/api-client.js'; import { extractProjectContext, generateIntelligentTitle, extractProgressIndicators, extractRelationships } from '../intelligent-memory.js'; import { WORKFLOW TEMPLATES, classifyWorkflowIntent, buildMemoryQueries } from '../workflows/engine.js'; ⋮---- let readCurrentSessionId: ⋮---- export function initHandlers deps: { platform: string; getLastRecallIds: ⋮---- let getLastRecallIds: let setLastRecallIds: ids: string = void = ids = ⋮---- function extractContentMetadata content ⋮---- function shouldChunk content ⋮---- function chunkContent conten… Evidence: `src/tools/handlers.ts`
- **Handoff** (source_file): import { structuredLog } from '../lib/logger.js'; import { makeApiCall, safeErrorMessage } from '../lib/api-client.js'; ⋮---- interface Memory { id: string; title: string; summary?: string; key result?: string; intent?: string; task type?: string; project name?: string; project component?: string; feature name?: string; status?: string; next phase hint?: string; primary intent?: string; decisions?: Decision ; work items?: WorkItem ; blockers?: Blocker ; completions?: Completion ; technologies?: string ; entities?: Entity ; context structured?: ContextStructured; content?: string; content preview?: string; created at?: string; updated at?: string; user updated at?: string; } ⋮---- interface… Evidence: `src/tools/handoff.ts`
- **Engine** (source_file): export function extractSearchTerms input, maxTerms = 5 ⋮---- export function buildMemoryQueries template, input ⋮---- export function classifyWorkflowIntent input Evidence: `src/workflows/engine.ts`
- **AI-Powered Recall Layer v1.3.0 — CoWork Test Results** (documentation): AI-Powered Recall Layer v1.3.0 — CoWork Test Results Evidence: `AI-Recall-Layer-v1.3.0-Test-Results.md`
- **Cluster Animation Implementation Context** (documentation): Cluster Animation Implementation Context Evidence: `ANIMATION_IMPLEMENTATION_CONTEXT.md`
- **Security Policy** (documentation): Version Supported ------- ------------------ 11.x :white check mark: < 11.0 :x: Evidence: `SECURITY.md`
- **Phase D Dry-Run Results** (documentation): Date: 2026-04-29 User scope: chris@purmemo.ai 3,152 memories, 83% of platform data Source: cluster-calibration/phase-d-dryrun.sql executed against live bcmsutoahlxqriealrjb DB writes: zero read-only simulation Evidence: `cluster-calibration/phase-d-dryrun-results.md`
- **Phase E — Sanity Check on Other Users** (documentation): Phase E — Sanity Check on Other Users Evidence: `cluster-calibration/phase-e-sanity-check.md`
- **Purmemo iOS - Session Log - March 29, 2026** (documentation): Purmemo iOS - Session Log - March 29, 2026 Evidence: `purmemo-ios/SESSION_LOG_2026-03-29.md`
- **/commit — Persist a commitment-shaped artifact** (documentation): /commit — Persist a commitment-shaped artifact Evidence: `.claude/commands/commit.md`
- **Session Startup & Project Context** (documentation): Description: Get comprehensive project context after time away from the project. Evidence: `.claude/commands/context.md`
- **Structured Debugging Workflow** (documentation): Description: Debug errors with research, context recall, and automatic solution documentation. Evidence: `.claude/commands/debug.md`
- **Architecture Decision Records ADRs** (documentation): Description: Make and document architectural decisions with research and structured ADR format. Evidence: `.claude/commands/decide.md`
- **Pre-Deployment Checklist** (documentation): Description: Comprehensive pre-deployment checks for safe production deployment to Render/Supabase. Evidence: `.claude/commands/deploy.md`
- **Workflow System Help** (documentation): Display the complete command reference for the Purmemo AI-Native Founder OS. Evidence: `.claude/commands/help.md`
- The remaining 19 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `.claude/README.md`, `CLAUDE.md`, `README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `.claude/README.md`, `CLAUDE.md`, `README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Installation, Sign-in & Auth Recovery**: importance `high`
  - source_paths: README.md, scripts/install.sh, scripts/install.ps1, src/setup.ts, src/auth/oauth-manager.ts
- **MCP Tools, Hooks & Slash Commands**: importance `high`
  - source_paths: src/server.ts, src/tools/handlers.ts, src/tools/handoff.ts, src/intelligent-memory.ts, src/workflows/engine.ts
- **Architecture & Key Design Decisions**: importance `high`
  - source_paths: ARCHITECTURE.md, CLAUDE.md, src/index.ts, src/types.ts, src/lib/api-client.ts
- **Cross-Platform Integrations, iOS & Distribution**: importance `medium`
  - source_paths: purmemo-ios/README.md, purmemo-ios/purmemo-ios/PurmemoApp.swift, purmemo-ios/purmemo-ios/Services/PurmemoAPI.swift, purmemo-ios/purmemo-ios/Services/AuthService.swift, purmemo-ios/purmemo-ios/Services/KeychainService.swift

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `504a92799ac2fe386fc65d7be24cc2fdff5de8ef`
- inspected_files: `README.md`, `package.json`, `docs/ENVIRONMENT_SETUP.md`, `docs/adr/ADR-009-part-intelligence-propagation.md`, `docs/adr/ADR-011-desktop-macos-distribution.md`, `docs/adr/ADR-016-recency-hybrid-recall-retrieval.md`, `docs/adr/ADR-017-mcp-distribution-parity.md`, `docs/adr/ADR-027-reranker-optimization-per-surface.md`, `docs/adr/ADR-031-api-key-leak-prevention-and-identity-binding.md`, `docs/adr/ADR-032-artifact-replacement-primitives.md`, `docs/adr/ADR-033-documentation-repository-architecture.md`, `docs/adr/ADR-037-cli-hook-platform-adapter-architecture.md`, `docs/adr/ADR-039-encryption-key-derivation.md`, `src/auth/install-detection.ts`, `src/auth/oauth-manager.ts`, `src/auth/profile-migrator.ts`, `src/auth/profile-resolver.ts`, `src/auth/setup-decisions.ts`, `src/auth/token-store.ts`, `src/auth/universal-auth.ts`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v15.7.15 — Codex hook parity
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.15 — Codex hook parity. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v15.7.15 — Codex hook parity
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.15
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v15.7.16 — enable Codex hooks feature flag
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.16 — enable Codex hooks feature flag. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v15.7.16 — enable Codex hooks feature flag
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.16
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v15.7.19 — Auto-recover from unrecoverable token decrypt
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.19 — Auto-recover from unrecoverable token decrypt. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v15.7.19 — Auto-recover from unrecoverable token decrypt
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.19
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: v15.7.20 — Zero-friction install + auto-recover from sign-in drift
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.20 — Zero-friction install + auto-recover from sign-in drift. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v15.7.20 — Zero-friction install + auto-recover from sign-in drift
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.20
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: v15.7.18 — auth: persisted encryption key
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.18 — auth: persisted encryption key. Context: Observed when using macos
- Why it matters: Upgrade or migration may change expected behavior: v15.7.18 — auth: persisted encryption key
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.18
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/purmemo-ai/purmemo-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Runtime risk requires verification

- Trigger: Developers should check this runtime risk before relying on the project: v15.7.22 — get_test_results no longer truncates failure body
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v15.7.22 — get_test_results no longer truncates failure body. Context: Observed when using node
- Why it matters: Upgrade or migration may change expected behavior: v15.7.22 — get_test_results no longer truncates failure body
- Evidence: failure_mode_cluster:github_release | https://github.com/purmemo-ai/purmemo-mcp/releases/tag/v15.7.22
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 8: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/purmemo-ai/purmemo-mcp
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.