Skip to content

proof-bundle.md

Latest commit

 

History

History
45 lines (33 loc) · 1.3 KB

proof-bundle.md

File metadata and controls

45 lines (33 loc) · 1.3 KB

Example: Proof Bundle

This example shows how MobileCodex gathers proof for a larger task.

Natural Requests

Users should be able to ask:

  • "Bundle this up."
  • "Save the proof."
  • "Make this resumable."
  • "What changed and what proves it?"
  • "I'm stepping away, leave me the state."

Representative Command

py .\skills\mobile-codex-dev\scripts\mobile_dev.py proof-bundle --root . --format markdown
py .\skills\mobile-codex-dev\scripts\mobile_dev.py final-flow --root . --test-result "<latest relevant command result>"

Bundle Should Include

  • Snapshot output.
  • Changed files.
  • Detected project shape.
  • Server registry state.
  • Recent proof artifacts.
  • Copied screenshots when safe and local.
  • Optional log tails when provided.
  • File sizes and absolute paths.

Handoff Shape

Result: Proof bundle created.
Preview: No public preview exposed.
Proof: `proof/mobilecodex-YYYYMMDD-HHMMSS/proof.md` contains snapshot, changed files, server state, artifacts, and log tails.
State: Bundle is local under `proof/` and can be referenced by future Codex Mobile sessions.
Next: Review the proof file or ask for a public preview if the app is safe to expose.

Why This Helps From Mobile

The user gets one durable proof folder instead of scattered screenshots, logs, and status snippets.