assertion-cli 0.5.6__tar.gz → 0.5.7__tar.gz

{assertion_cli-0.5.6 → assertion_cli-0.5.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: assertion-cli
-Version: 0.5.6
+Version: 0.5.7
 Summary: CLI for the Assertion API
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown

{assertion_cli-0.5.6 → assertion_cli-0.5.7}/assertion_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: assertion-cli
-Version: 0.5.6
+Version: 0.5.7
 Summary: CLI for the Assertion API
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown

{assertion_cli-0.5.6 → assertion_cli-0.5.7}/pyproject.toml

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

{assertion_cli-0.5.6 → assertion_cli-0.5.7}/templates/SKILL.md

@@ -16,7 +16,16 @@ Before any `asrt` call:
 - You are inside a git repository.
 - `asrt init` has been run in this repo. It records the current HEAD as the diff base that every checkpoint/verify diffs against, and installs the skill files you are reading right now. If `asrt checkpoint` or `asrt verify` errors with "No diff base recorded", run `asrt init` and retry.
 
-**Starting a fresh session:** when beginning a new work session, check whether this repo may have previous Assertion state in `.assertion/`, then ask the user whether they want to clean up the previous session and start fresh. If the user says yes, run `asrt new` before any checkpoint or verify command. This clears the previous session's in-flight state (metadata, prompts log, link, verification status, screenshots) and records the current `HEAD` as the new diff base, so a new session starts clean on the current branch and anchors to the stack you pick on the first checkpoint. If the user says no, continue with the existing session state. Do not run `asrt new` without explicit user consent — it resets the session.
+**First command sequence for a new work session:**
+
+1. Before any `asrt` call, check whether this repo may have previous Assertion state in `.assertion/`.
+2. If previous Assertion state exists, ask the user: "Do you want to clean up the previous Assertion session and start fresh?"
+3. When the harness supports structured prompts or selectable options, present the question with selectable `Yes` and `No` options. Do not ask the user to type `yes` or `no` unless selectable options are unavailable.
+4. If the user answers yes, run `asrt new` before any other `asrt` command.
+5. If the user answers no, continue with the existing session state.
+6. After the reset decision is resolved, immediately log the active user prompt with `asrt prompt`. Treat the cleanup confirmation itself as a control response, not user intent to record, when it only answers this reset question.
+
+This check is the only allowed exception to Rule 1's "first thing" requirement: resolve it before the first `asrt prompt` call, because `asrt new` clears the prompts log. `asrt new` clears the previous session's in-flight state (metadata, prompts log, link, verification status, screenshots) and records the current `HEAD` as the new diff base, so a new session starts clean on the current branch and anchors to the stack you pick on the first checkpoint. Do not run `asrt new` without explicit user consent — it resets the session.
 
 Treat `.assertion/metadata.json`, `.assertion/prompts`, and `.assertion/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 new` to reset for a fresh session.
 
@@ -32,6 +41,8 @@ Treat `.assertion/metadata.json`, `.assertion/prompts`, and `.assertion/base_sha
 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. If the user approves a reset, run `asrt new` before `asrt prompt`; otherwise skip the reset. Once that decision is resolved, immediately run `asrt prompt` for the active user message so the new/current session records the user's intent. If the only separate user message during preflight is a plain reset confirmation, do not record that confirmation as its own prompt.
+
 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.

{assertion_cli-0.5.6 → assertion_cli-0.5.7}/tests/test_init.py

@@ -178,8 +178,37 @@ def test_init_skill_prompts_before_new_session_cleanup(
     skill = (
         tmp_path / ".agents" / "skills" / "assertion-cli" / "SKILL.md"
     ).read_text()
-    assert "ask the user whether they want to clean up the previous session" in skill
-    assert "If the user says yes, run `asrt new` before any checkpoint" in skill
+    assert "First command sequence for a new work session" in skill
+    assert (
+        'ask the user: "Do you want to clean up the previous Assertion session '
+        'and start fresh?"'
+    ) in skill
+    assert (
+        "present the question with selectable `Yes` and `No` options"
+    ) in skill
+    assert (
+        "Do not ask the user to type `yes` or `no` unless selectable options "
+        "are unavailable"
+    ) in skill
+    assert (
+        "resolve it before the first `asrt prompt` call, because `asrt new` clears "
+        "the prompts log"
+    ) in skill
+    assert (
+        "If the user answers yes, run `asrt new` before any other `asrt` command"
+    ) in skill
+    assert (
+        "After the reset decision is resolved, immediately log the active user prompt "
+        "with `asrt prompt`"
+    ) in skill
+    assert (
+        "Treat the cleanup confirmation itself as a control response, not user intent "
+        "to record"
+    ) in skill
+    assert (
+        "If the only separate user message during preflight is a plain reset "
+        "confirmation, do not record that confirmation as its own prompt"
+    ) in skill
     assert "Do not run `asrt new` without explicit user consent" in skill
     assert "After the PR marker is confirmed" in skill
     assert "clean up the completed Assertion session" in skill