Maester Save Snapshot Report

Summary

• completed_at: 2026-05-09T16:45:00+09:00
• scope: Maester v3.1 through v5.0 code, prompts, handoffs, and context logs
• database contents: excluded
• secrets: .env excluded; historical token literals redacted before commit
• runtime: maester-api restarted and runtime truth passed
• latest product loop: v5.0 Revenue Event Capture Loop remains complete

GitHub

Included

• maester-agent: API/MCP source, graph client, ingest/recall tools, eval scripts, v3.4-v5.1 handoffs, OpenAPI spec, prompts, approval templates, test fixtures.
• maester: chat-log prompts and decision context from v3 through v5.0, draft/prompt/script support files.

Excluded

• .env, .env.*
• .venv, __pycache__, compiled Python files
• DB files and dumps: *.db, *.sqlite*, *.dump, backup files
• maester/data/ entirely, including Supabase exports, voice/audio archive, vault, and local indexes
• maester-agent/data/docs/ document-store runtime contents
• runtime queues/audits/idempotency state, including Tiro queues and generated approval files

Verification

• py_compile: passed for changed Maester API/server and v5.0 scripts.
• scripts/runtime_truth.py: PASS.
• /api/health: ok, Neo4j ok, systemd user unit maester-api.service, git commit 83bcb18.
• v5.0 revenue event counts remain: real=0, test=5.

Notes

• The existing v5.0 result remains available at https://ai.shinjadong.cloud/export/msg_20260509_681e1354.md.
• ChatGPT handoff automation stopped at the current quota message, so no v5.1 instruction was received yet.