Skip to content

v1.3.1 - Verifiable context continuity and advisor routing

Choose a tag to compare

@rumotion rumotion released this 09 Nov 19:50
· 13 commits to main since this release

v1.3.1 - Verifiable context continuity and advisor routing

This release adds verifiable cross-session continuity, a private durable task
ledger with separate parent acceptance, offline advisor model routing (R1),
a smaller startup footprint, and native hook repairs across Antigravity,
Claude and Codex on Windows and Linux.

Patch v1.3.1 also canonicalizes Windows 8.3 short-path and junction aliases
in scripts/hooks/log-writes.py when comparing event cwd/target paths
against resolved workspace roots on Windows CI runners.

Highlights

  • Verifiable context continuity (scripts/continuity.py, scripts/ctx.py):
    private checkpoints, strict resume diagnostics (doctor), visible redacted
    lifecycle failures, required-record protection and task/archive projections
    scaling to 1,000 archived records within the startup budget cap.
  • Durable task ledger (scripts/tasks.py, scripts/task_metrics.py):
    track task revisions, attempts, dependency gates and file-scope inventories;
    keep worker submission separate from parent acceptance; measure ordinary task
    progress and counters with quota pacing OFF.
  • Offline advisor escalation policy (scripts/routing_policy.py):
    deterministic R1 routing between a fast implementation model and a read-only
    senior advisor for material plans, completion review and repeated logic errors,
    with review receipts bound to task revision, attempt, artifact hash and error ID.
  • Smaller startup and native client fixes: compacted memory-bank/00-index.md
    from 1,534 to 619 characters (FAST_INIT ~7,710/9,500 chars), fixed
    CWD-independent Antigravity hook launch and write_file/Path aliases,
    repaired Windows PowerShell hook execution for Codex, canonicalized Windows
    path aliases in log-writes.py, and enabled local Git core.longpaths
    during Windows project bootstrap.

How to start a new project

python scripts/new-project.py ../my-project --name "My Project"
cd ../my-project
python scripts/init-fast.py

Open ../my-project in your coding agent and start with:
FAST_INIT (default mode per AGENTS.md).

How to quickly upgrade an existing project

1. First-time upgrade (or installing into an existing repo)

Open your existing project in Claude Code, Codex, or Antigravity and paste:

Upgrade this project's AI framework from
https://github.com/rumotion/ai-agent-project-template using its latest upgrade
workflow. Preserve application code, tests, settings, custom rules, skills and
project memory. Preview changes, resolve conflicts and run the project's checks.
Do not push or deploy.

2. Subsequent upgrades (one sentence)

After the first remote upgrade, the project remembers the template source and
file hashes in .template-upstream.json. Next time, simply ask your agent:

Update this project from its saved AI template source and verify the result locally.

3. Direct CLI preview and apply

python scripts/upgrade-target.py --target ../existing-project --dry-run
python scripts/upgrade-target.py --target ../existing-project

Verification and limits

Full validation (python scripts/check-template.py) covers 193 required files,
10 instruction adapters, 17 context budgets, 22 skills across 3 discovery trees,
and 15 hardening/recovery suites. Scoped native evidence for Antigravity IDE/CLI,
Claude CLI and Codex CLI is documented in
docs/recovery-pilot.md.
Unverified cold-restart, standalone-app and multi-writer fleet surfaces remain
explicit future work.

Upgrade guide
| Continuity guide
| Changes since v1.2.1.