assertion-cli 0.5.14__tar.gz → 0.5.15__tar.gz

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: assertion-cli
-Version: 0.5.14
+Version: 0.5.15
 Summary: CLI for the Assertion API
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
@@ -42,7 +42,6 @@ After installation:
 asrt install                           # one-time onboarding: write skill files, AGENTS.md/CLAUDE.md pointer, .gitignore
 asrt login                             # authenticate this repo (generate a token at Settings → Authentication)
 asrt session start                     # per work session: record the diff base (current HEAD)
-asrt new                               # reset local run state for a fresh session
 asrt stacks
 asrt checkpoint --stack <stack-id> "Implemented X\nUpdated Y"
 asrt checkpoint --continue "Implemented Y"

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/README.md

@@ -29,7 +29,6 @@ After installation:
 asrt install                           # one-time onboarding: write skill files, AGENTS.md/CLAUDE.md pointer, .gitignore
 asrt login                             # authenticate this repo (generate a token at Settings → Authentication)
 asrt session start                     # per work session: record the diff base (current HEAD)
-asrt new                               # reset local run state for a fresh session
 asrt stacks
 asrt checkpoint --stack <stack-id> "Implemented X\nUpdated Y"
 asrt checkpoint --continue "Implemented Y"

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/assertion_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: assertion-cli
-Version: 0.5.14
+Version: 0.5.15
 Summary: CLI for the Assertion API
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
@@ -42,7 +42,6 @@ After installation:
 asrt install                           # one-time onboarding: write skill files, AGENTS.md/CLAUDE.md pointer, .gitignore
 asrt login                             # authenticate this repo (generate a token at Settings → Authentication)
 asrt session start                     # per work session: record the diff base (current HEAD)
-asrt new                               # reset local run state for a fresh session
 asrt stacks
 asrt checkpoint --stack <stack-id> "Implemented X\nUpdated Y"
 asrt checkpoint --continue "Implemented Y"

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/main.py

@@ -469,7 +469,8 @@ def session_start(
 
     typer.echo("")
     typer.echo("The coding agent will now follow the Assertion workflow:")
-    typer.echo('  - asrt prompt "<msg>" on every user turn')
+    typer.echo('  - in non-Plan mode, asrt prompt "<msg>" for each user turn')
+    typer.echo('  - when starting from a finalized plan, log it with asrt prompt')
     typer.echo("  - asrt checkpoint at trajectory-feedback moments")
     typer.echo("  - asrt verify at completion, then PR")
 

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "assertion-cli"
-version = "0.5.14"
+version = "0.5.15"
 description = "CLI for the Assertion API"
 readme = "README.md"
 requires-python = ">=3.13"

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/templates/AGENTS.md

@@ -5,9 +5,9 @@ This repo uses the Assertion CLI (`asrt`) to track user intent and verify your w
 - **Claude Code** — [`.claude/skills/assertion-cli/SKILL.md`](.claude/skills/assertion-cli/SKILL.md)
 - **Codex / Cursor** — [`.agents/skills/assertion-cli/SKILL.md`](.agents/skills/assertion-cli/SKILL.md)
 
-Both files are byte-identical — read whichever your agent loads (or either one directly). In brief, follow these three rules for every conversation:
+Both files are byte-identical — read whichever your agent loads (or either one directly). In brief, follow these three rules in non-Plan mode:
 
-1. **Every user message:** call `asrt prompt "<exact text of the message>"` before doing any other work for that turn. Apply to every user turn, not just the first.
+1. **Prompts:** do not call `asrt prompt` during Plan Mode. When implementation begins from a finalized plan, record that plan with `asrt prompt "<finalized plan text>"`; after that, call `asrt prompt "<exact text of the message>"` for each non-Plan user turn before doing other work.
 2. **Checkpoint at trajectory-feedback moments** with `asrt checkpoint` — a handful across a feature build, not one per file.
 3. **Verify, then PR with the session marker.** At completion, run `asrt verify` and poll `asrt verify-status` until clean. Then open the PR and embed the hidden session marker — `$(asrt get-link)`, an HTML comment — in its body.
 

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/templates/SKILL.md

@@ -1,14 +1,20 @@
 ---
 name: assertion-cli
-description: Use this skill in non-Plan mode whenever working in a repo that uses the Assertion CLI (`asrt`). It enforces the three-rule workflow — log every user message with `asrt prompt`, checkpoint at trajectory-feedback moments (not on every change), and verify only at completion before opening a PR whose body embeds the hidden Assertion session marker. Applies to any coding agent reading this skill.
+description: Use this skill in non-Plan mode whenever working in a repo that uses the Assertion CLI (`asrt`). It enforces the three-rule workflow — log non-Plan user messages and finalized implementation plans with `asrt prompt`, checkpoint at trajectory-feedback moments (not on every change), and verify only at completion before opening a PR whose body embeds the hidden Assertion session marker. Applies to any coding agent reading this skill.
 ---
 
 # Assertion CLI
 
-You are operating in a repo that uses the Assertion CLI (`asrt`) to track user intent and verify your work. Follow the three rules below without exception. They apply regardless of which coding agent harness you are running under (Claude Code, Codex, Cursor, etc.).
+You are operating in a repo that uses the Assertion CLI (`asrt`) to track user intent and verify your work. Follow the three rules below without exception in non-Plan mode. They apply regardless of which coding agent harness you are running under (Claude Code, Codex, Cursor, etc.).
 
 This skill is operational, not advisory. Treat each rule as a hard requirement unless the underlying service is unavailable.
 
+## Plan Mode boundary
+
+When the harness is in Plan Mode, do not run `asrt prompt`, `asrt checkpoint`, `asrt verify`, or PR commands. Plan Mode is for producing a plan, not for mutating Assertion session state.
+
+When the harness leaves Plan Mode and begins implementation from a finalized plan, first record that plan with `asrt prompt "<finalized plan text>"`. Then proceed with the non-Plan workflow below, including logging any later user messages as they arrive.
+
 ## Preflight (one-time per session)
 
 Before any `asrt` call:
@@ -21,7 +27,8 @@ Before any `asrt` call:
 **First command sequence for a new work session:**
 
 1. Run `asrt session start` to start fresh. This clears previous in-flight Assertion state (metadata, prompts log, link, verification status, screenshots) and records the current verification base.
-2. Immediately log the active user prompt with `asrt prompt`.
+2. If starting from a finalized Plan Mode plan, immediately log that plan with `asrt prompt`.
+3. Otherwise, immediately log the active non-Plan user prompt with `asrt prompt`.
 
 Treat `.assertion/metadata.json`, `.assertion/prompts`, and `.assertion/verify_base_sha` as internal state owned by the CLI. Do not create, edit, or delete those files manually — use `asrt prompt` to append to the prompts log and `asrt session start` to reset for a fresh session.
 
@@ -29,17 +36,23 @@ Treat `.assertion/metadata.json`, `.assertion/prompts`, and `.assertion/verify_b
 
 ---
 
-## Rule 1 — Log every user message, immediately
+## Rule 1 — Log non-Plan user messages and finalized plans, immediately
 
-**The first thing you do when a new user message arrives — before reading any file, planning, or editing anything — is run:**
+**In non-Plan mode, the first thing you do when a new user message arrives — before reading any file, planning, or editing anything — is run:**
 
 ```
 asrt prompt "<exact text of the user's message>"
 ```
 
-Exception: on the first user turn of a new work session, perform the Preflight fresh-session check first by running `asrt session start`, then immediately run `asrt prompt` for the active user message so the new/current session records the user's intent.
+Plan Mode exception: if the harness is currently in Plan Mode, do not call `asrt prompt` for each planning turn. When implementation begins from the finalized plan, record the plan itself as the first prompt:
+
+```
+asrt prompt "<finalized plan text>"
+```
+
+Fresh-session exception: on the first non-Plan user turn of a new work session, perform the Preflight fresh-session check first by running `asrt session start`, then immediately run `asrt prompt` for the active user message or finalized plan so the new/current session records the user's intent.
 
-This applies to **every user turn**, not just the first. It applies even when the message is a one-word direction change ("nope"), a clarification ("use Postgres, not SQLite"), or a follow-up after verify ("also add dark mode").
+Outside Plan Mode, this applies to **every user turn**, not just the first. It applies even when the message is a one-word direction change ("nope"), a clarification ("use Postgres, not SQLite"), or a follow-up after verify ("also add dark mode").
 
 **Why:** The prompts log is the verifier's source of truth for what the user asked for and how their direction evolved. It is shipped with every checkpoint and the final verify, and persisted in the verification database. A missed turn causes the verifier to flag legitimate work as off-spec because it cannot see the intent change that authorized the work.
 
@@ -207,7 +220,7 @@ A missing marker is a **blocking error**, not a warning: do not consider the PR
 ## Quick reference
 
 ```
-asrt prompt "<message>"                       # every user turn, before anything else
+asrt prompt "<message>"                       # non-Plan user turn or finalized plan, before work
 asrt session start [--from <ref>]             # start fresh; optional explicit verification base
 asrt stacks                                   # list every stack — read once before first checkpoint
 asrt checkpoint --stack <id> "..."            # first checkpoint of a session

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/tests/test_install.py

@@ -47,6 +47,9 @@ def test_install_writes_agent_doc_pointers(tmp_path: Path, monkeypatch) -> None:
         assert main._AGENT_BLOCK_END in text
         assert "assertion-cli" in text
         assert "asrt prompt" in text
+        assert "do not call `asrt prompt` during Plan Mode" in text
+        assert "finalized plan" in text
+        assert "**Every user message:**" not in text
 
 
 def test_install_preserves_existing_agent_doc_content(
@@ -132,6 +135,12 @@ def test_install_records_skill_cleanup_guidance(tmp_path: Path, monkeypatch) ->
     skill = (tmp_path / ".agents" / "skills" / "assertion-cli" / "SKILL.md").read_text()
     assert "First command sequence for a new work session" in skill
     assert "`asrt session start`" in skill
+    assert "## Plan Mode boundary" in skill
+    assert (
+        "do not run `asrt prompt`, `asrt checkpoint`, `asrt verify`, or PR commands"
+        in skill
+    )
+    assert 'asrt prompt "<finalized plan text>"' in skill
     assert "`asrt new`" not in skill
 
 

{assertion_cli-0.5.14 → assertion_cli-0.5.15}/tests/test_session_start.py

@@ -66,6 +66,26 @@ def test_session_start_does_not_write_skill_or_agent_files(
     assert not (tmp_path / "AGENTS.md").exists()
 
 
+def test_session_start_prints_non_plan_prompt_workflow(
+    tmp_path: Path, monkeypatch
+) -> None:
+    _init_repo(tmp_path)
+    monkeypatch.chdir(tmp_path)
+
+    result = runner.invoke(main.app, ["session", "start"])
+    assert result.exit_code == 0, result.stderr
+
+    assert (
+        'in non-Plan mode, asrt prompt "<msg>" for each user turn'
+        in result.stdout
+    )
+    assert (
+        "when starting from a finalized plan, log it with asrt prompt"
+        in result.stdout
+    )
+    assert 'asrt prompt "<msg>" on every user turn' not in result.stdout
+
+
 def test_session_start_resets_assertion_state_but_keeps_seed_trackable(
     tmp_path: Path, monkeypatch
 ) -> None: