tycho-cli 0.0.1__tar.gz → 0.0.3__tar.gz

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/.gitignore

@@ -234,3 +234,6 @@ __marimo__/
 .private/
 /CLAUDE.md
 /AGENTS.md
+
+# Local dev toggle (per-machine paths); commit tycho-target.ps1.example instead.
+/tycho-target.ps1

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tycho-cli
-Version: 0.0.1
+Version: 0.0.3
 Summary: Tycho — a free, offline, open-source local verifier that proves an AI agent actually did what it claims, from git, the filesystem, process exit codes, and the harness event stream. No account, no LLM in the trust path.
 Project-URL: Homepage, https://swail.dev/tycho
 Project-URL: Repository, https://github.com/swail-labs/tycho
@@ -97,7 +97,7 @@ it can't parse rather than risk it.
 
 On Claude Code it also adds a status-bar badge and a set of `/tycho` slash commands, so you can see it's
 on and drive it without leaving the session — see [In Claude Code](#in-claude-code) below. On the other
-three harnesses, `tycho status` prints that same badge for a shell prompt or tmux status line — see
+three harnesses, `tycho statusline` prints that same badge for a shell prompt or tmux status line — see
 [The badge in any shell](#the-badge-in-any-shell).
 
 That's it. The next time an agent finishes a turn, Tycho verifies it automatically and prints the
@@ -109,7 +109,7 @@ tycho verify --harness cursor    # force a harness (default: whichever ran most
 tycho verify --session <path>    # verify a specific transcript
 tycho verify --claim "added rate limiting, tests pass"   # echo the claim above the verdict
 tycho help                       # what Tycho is, whether it's live here, and every command
-tycho status                     # the one-line status-bar indicator (what Claude Code renders)
+tycho statusline                     # the one-line status-bar indicator (what Claude Code renders)
 tycho count                      # how many problems Tycho has caught — in this repo, and all-time
 tycho run -- pytest -q           # run a command so its true exit code is seen (see "tycho run" below)
 tycho scope list                 # show/edit which files the agent may edit (see "Scope" below)
@@ -227,8 +227,8 @@ already run a status line — a third-party badge, a shell prompt — Tycho **co
 replacing it: it takes Claude Code's single `statusLine` slot, runs your existing command too, and renders
 both (`[OTHER] [TYCHO]`). Nothing you had is lost, and `tycho uninstall` restores it.
 
-**Toggle the badge.** `/tycho-hide` (or `tycho status --off`) hides only Tycho's segment — the hook keeps
-verifying every turn; `/tycho-show` (or `tycho status --on`) brings it back. `TYCHO_STATUS=off` hides it
+**Toggle the badge.** `/tycho-hide` (or `tycho statusline --off`) hides only Tycho's segment — the hook keeps
+verifying every turn; `/tycho-show` (or `tycho statusline --on`) brings it back. `TYCHO_STATUS=off` hides it
 everywhere for a session.
 
 ## Let the agent see its own verdict — the relay
@@ -275,23 +275,23 @@ the cheapest, quietest default; turn it on when you'd rather the agent fix a bad
 
 Only the *wiring* is Claude-only. `statusLine` is the one harness setting that means "run this command and
 render its stdout", so `tycho init` has nowhere to hang the badge on Cursor, Codex, or OpenCode. The badge
-itself doesn't care: `tycho status` reads `.tycho/` off disk and prints one line, whichever agent wrote the
+itself doesn't care: `tycho statusline` reads `.tycho/` off disk and prints one line, whichever agent wrote the
 state. Call it from anything that renders a command:
 
 ```sh
-PS1='$(tycho status) '$PS1                                        # bash / zsh prompt
-set -g status-right '#(cd #{pane_current_path} && tycho status)'  # tmux (in tmux.conf)
+PS1='$(tycho statusline) '$PS1                                        # bash / zsh prompt
+set -g status-right '#(cd #{pane_current_path} && tycho statusline)'  # tmux (in tmux.conf)
 ```
 
 ```toml
 [custom.tycho]                                # starship (in starship.toml)
-command = "tycho status"
+command = "tycho statusline"
 when = true
 ```
 
 No stdin needed — with no JSON on stdin it resolves the repo from the current directory, walking up to
 find `.tycho/`, so the badge stays put as you `cd` around the tree. It prints nothing in repos where
-Tycho isn't installed, so it stays out of every other prompt you have. `tycho status --off` / `--on` and
+Tycho isn't installed, so it stays out of every other prompt you have. `tycho statusline --off` / `--on` and
 `TYCHO_STATUS=off` work here exactly as they do in Claude Code.
 
 ## Is the hook still firing?

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/README.md

@@ -71,7 +71,7 @@ it can't parse rather than risk it.
 
 On Claude Code it also adds a status-bar badge and a set of `/tycho` slash commands, so you can see it's
 on and drive it without leaving the session — see [In Claude Code](#in-claude-code) below. On the other
-three harnesses, `tycho status` prints that same badge for a shell prompt or tmux status line — see
+three harnesses, `tycho statusline` prints that same badge for a shell prompt or tmux status line — see
 [The badge in any shell](#the-badge-in-any-shell).
 
 That's it. The next time an agent finishes a turn, Tycho verifies it automatically and prints the
@@ -83,7 +83,7 @@ tycho verify --harness cursor    # force a harness (default: whichever ran most
 tycho verify --session <path>    # verify a specific transcript
 tycho verify --claim "added rate limiting, tests pass"   # echo the claim above the verdict
 tycho help                       # what Tycho is, whether it's live here, and every command
-tycho status                     # the one-line status-bar indicator (what Claude Code renders)
+tycho statusline                     # the one-line status-bar indicator (what Claude Code renders)
 tycho count                      # how many problems Tycho has caught — in this repo, and all-time
 tycho run -- pytest -q           # run a command so its true exit code is seen (see "tycho run" below)
 tycho scope list                 # show/edit which files the agent may edit (see "Scope" below)
@@ -201,8 +201,8 @@ already run a status line — a third-party badge, a shell prompt — Tycho **co
 replacing it: it takes Claude Code's single `statusLine` slot, runs your existing command too, and renders
 both (`[OTHER] [TYCHO]`). Nothing you had is lost, and `tycho uninstall` restores it.
 
-**Toggle the badge.** `/tycho-hide` (or `tycho status --off`) hides only Tycho's segment — the hook keeps
-verifying every turn; `/tycho-show` (or `tycho status --on`) brings it back. `TYCHO_STATUS=off` hides it
+**Toggle the badge.** `/tycho-hide` (or `tycho statusline --off`) hides only Tycho's segment — the hook keeps
+verifying every turn; `/tycho-show` (or `tycho statusline --on`) brings it back. `TYCHO_STATUS=off` hides it
 everywhere for a session.
 
 ## Let the agent see its own verdict — the relay
@@ -249,23 +249,23 @@ the cheapest, quietest default; turn it on when you'd rather the agent fix a bad
 
 Only the *wiring* is Claude-only. `statusLine` is the one harness setting that means "run this command and
 render its stdout", so `tycho init` has nowhere to hang the badge on Cursor, Codex, or OpenCode. The badge
-itself doesn't care: `tycho status` reads `.tycho/` off disk and prints one line, whichever agent wrote the
+itself doesn't care: `tycho statusline` reads `.tycho/` off disk and prints one line, whichever agent wrote the
 state. Call it from anything that renders a command:
 
 ```sh
-PS1='$(tycho status) '$PS1                                        # bash / zsh prompt
-set -g status-right '#(cd #{pane_current_path} && tycho status)'  # tmux (in tmux.conf)
+PS1='$(tycho statusline) '$PS1                                        # bash / zsh prompt
+set -g status-right '#(cd #{pane_current_path} && tycho statusline)'  # tmux (in tmux.conf)
 ```
 
 ```toml
 [custom.tycho]                                # starship (in starship.toml)
-command = "tycho status"
+command = "tycho statusline"
 when = true
 ```
 
 No stdin needed — with no JSON on stdin it resolves the repo from the current directory, walking up to
 find `.tycho/`, so the badge stays put as you `cd` around the tree. It prints nothing in repos where
-Tycho isn't installed, so it stays out of every other prompt you have. `tycho status --off` / `--on` and
+Tycho isn't installed, so it stays out of every other prompt you have. `tycho statusline --off` / `--on` and
 `TYCHO_STATUS=off` work here exactly as they do in Claude Code.
 
 ## Is the hook still firing?

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/docs/harness-support.md

@@ -140,7 +140,7 @@ PY
 
 Two claims that are easy to conflate, and only the second is Claude-only (TYCHO-46):
 
-- **The command is harness-agnostic.** `tycho status` reads `.tycho/` off disk, imports no
+- **The command is harness-agnostic.** `tycho statusline` reads `.tycho/` off disk, imports no
   engine, and falls back to the cwd when there's no JSON on stdin (`status.repo_of`) — so a
   shell prompt, tmux, or starship renders the same badge on any of the four. Nothing below
   applies to that path; there's no harness in it. (It walks up from the cwd for `.tycho/`,
@@ -172,7 +172,7 @@ declaration and the execution rules from the call site, both verbatim:
 Two consequences worth keeping in mind:
 
 - **Exit 0 or it's dead.** A non-zero exit makes the harness ignore stdout entirely — the
-  same class of silent nothing as a dead output field. `tycho status` therefore catches
+  same class of silent nothing as a dead output field. `tycho statusline` therefore catches
   everything and returns 0 with empty output, which renders as nothing.
 - **Windows: the command runs through Git Bash**, which consumes unquoted backslashes;
   the harness's own guidance is to write paths with forward slashes. Our commands come

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tests/test_init_safety.py

@@ -143,7 +143,7 @@ def test_command_for_forward_slashes_windows_paths(monkeypatch):
 
     # console-script branch (tycho.exe on PATH) is forward-slashed too
     monkeypatch.setattr(init_mod.shutil, "which", lambda name: r"C:\Tools\tycho.exe")
-    assert init_mod.status_command() == "C:/Tools/tycho.exe status"
+    assert init_mod.status_command() == "C:/Tools/tycho.exe statusline"
 
 
 # --- SessionStart hook (TYCHO-53) --------------------------------------------

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tests/test_status.py

@@ -310,7 +310,7 @@ def test_init_claims_the_slot_when_it_is_free(tmp_path: Path):
     _install(tmp_path)
     settings = json.loads((tmp_path / CLAUDE).read_text())
     assert settings["statusLine"]["type"] == "command"
-    assert settings["statusLine"]["command"].endswith("status")
+    assert settings["statusLine"]["command"].endswith("statusline")
 
 
 def test_init_composes_with_a_repo_level_statusline_and_restores_it(tmp_path: Path):
@@ -323,7 +323,7 @@ def test_init_composes_with_a_repo_level_statusline_and_restores_it(tmp_path: Pa
     lines = init_mod.init(tmp_path, only="claude", assume_yes=True)
 
     assert "composing with your existing status line" in "\n".join(lines)
-    assert json.loads((tmp_path / CLAUDE).read_text())["statusLine"]["command"].endswith("status")
+    assert json.loads((tmp_path / CLAUDE).read_text())["statusLine"]["command"].endswith("statusline")
     wrap = state.read_statusline_wrap(tmp_path)
     assert wrap["command"] == theirs["command"] and wrap["origin"] == "repo"
 

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tycho/__init__.py

@@ -6,4 +6,4 @@ trust path. Free, open source (Apache 2.0), offline, no account needed.
 """
 
 # Alpha. Bumped to 0.1.0 for the first public release (TYCHO-10).
-__version__ = "0.0.1"
+__version__ = "0.0.3"

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tycho/cli.py

@@ -41,7 +41,7 @@ _COMMANDS = {
     "init": "install Tycho's hook into this repo's detected harnesses",
     "doctor": "check that Tycho's hooks are installed, current, and firing",
     "uninstall": "remove Tycho's hooks (leaves your other hooks alone)",
-    "status": "one line for a harness status bar: is Tycho live here, and the last verdict",
+    "statusline": "one line for a harness status bar: is Tycho live here, and the last verdict",
     "count": "how many problems Tycho has caught — in this repo, and all-time",
     "run": "run a command so its true exit code is seen even when wrapped/piped: tycho run -- pytest",
     "scope": "show or edit which files the agent may edit (the scope_drift allowlist)",
@@ -119,7 +119,10 @@ def main(argv: Sequence[str] | None = None) -> int:
         action="store_true",
         help="also delete repo-local Tycho state (.tycho/) and config (.tycho.toml)",
     )
-    s = sub.add_parser("status", help=_COMMANDS["status"])
+    # `status` stays as a hidden back-compat alias: deployed statusLine entries and slash
+    # commands (/tycho-status, --off/--on) still say `status`, and this tool ships to installs
+    # that already have them (TYCHO-108).
+    s = sub.add_parser("statusline", aliases=["status"], help=_COMMANDS["statusline"])
     toggle = s.add_mutually_exclusive_group()
     toggle.add_argument("--off", action="store_true", help="hide the indicator in this repo (the hook keeps verifying)")
     toggle.add_argument("--on", action="store_true", help="show the indicator again")
@@ -169,7 +172,7 @@ def main(argv: Sequence[str] | None = None) -> int:
         return _update(skip=args.skip)
     if args.command == "relay":
         return _relay(Path.cwd(), on=args.on, off=args.off)
-    if args.command == "status":
+    if args.command in ("statusline", "status"):
         from . import status
 
         return status.main(off=args.off, on=args.on)

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tycho/doctor.py

@@ -35,6 +35,7 @@ import time
 from dataclasses import dataclass
 from pathlib import Path
 
+from . import __version__
 from . import harness as harness_mod
 from . import init as init_mod
 from . import state
@@ -292,7 +293,7 @@ def healthy(findings: list[Finding]) -> bool:
 
 
 def render(findings: list[Finding]) -> str:
-    lines = ["tycho doctor"]
+    lines = [f"tycho doctor (v{__version__})"]
     for f in findings:
         mark = {OK: "✓", INFO: "•", DRIFT: "⚠"}.get(f.level, "✗")
         label = "" if f.level in (OK, INFO, DRIFT) else f"{f.level}: "

{tycho_cli-0.0.1 → tycho_cli-0.0.3}/tycho/init.py

@@ -96,7 +96,7 @@ def hook_command() -> str:
 
 def status_command() -> str:
     """Same resolution as `hook_command`, for the status bar (TYCHO-39)."""
-    return _command_for("status")
+    return _command_for("statusline")
 
 
 def _command_for(subcommand: str) -> str:
@@ -150,7 +150,10 @@ def _is_tycho_hook(command: object) -> bool:
 
 
 def _is_tycho_status(command: object) -> bool:
-    return _is_ours(command, "status")
+    # `statusline` is canonical; `status` is the pre-TYCHO-108 name. Match both so init
+    # self-heals an old `tycho status` statusLine into `tycho statusline`, and uninstall
+    # removes it either way.
+    return _is_ours(command, "statusline") or _is_ours(command, "status")
 
 
 def _is_tycho_session_start(command: object) -> bool:
@@ -576,13 +579,13 @@ def _install_claude(repo: Path) -> str:
 # each shows up with its own description in Claude Code's `/` autocomplete (TYCHO-48).
 # `hide`/`show` are the discoverable face of the `tycho status --off/--on` toggle (TYCHO-47).
 _SLASH_SUBCOMMANDS = {
-    "status": ("Is Tycho live here, and its last verdict", "status"),
+    "status": ("Is Tycho live here, and its last verdict", "statusline"),
     "doctor": ("Full diagnostics: is Tycho installed, current, and firing?", "doctor"),
     "verify": ("Verify the latest session and render a verdict", "verify $ARGUMENTS"),
     "help": ("What Tycho is, whether it's live here, and every command", "help"),
     "count": ("How many problems Tycho has caught here, and all-time", "count"),
-    "hide": ("Hide the Tycho status indicator (the hook keeps verifying)", "status --off"),
-    "show": ("Show the Tycho status indicator again", "status --on"),
+    "hide": ("Hide the Tycho status indicator (the hook keeps verifying)", "statusline --off"),
+    "show": ("Show the Tycho status indicator again", "statusline --on"),
     "relay": ("Is the verdict relay on? (agent sees its verdict, works till VERIFIED)", "relay"),
     "relay-on": ("Turn ON the verdict relay — agent sees non-VERIFIED verdicts, works till VERIFIED (bounded)", "relay --on"),
     "relay-off": ("Turn OFF the verdict relay — verdicts stay human-only (the default)", "relay --off"),

tycho_cli-0.0.3/tycho-target.ps1.example

@@ -0,0 +1,19 @@
+# Toggle tycho hooks/statusline between local editable venv and global uv-tool release.
+# Copy to tycho-target.ps1 (gitignored) and run from the repo root.
+# Usage: .\tycho-target.ps1   (flips)   |   .\tycho-target.ps1 local   |   .\tycho-target.ps1 release
+$settings = Join-Path $PSScriptRoot ".claude\settings.json"
+$local   = (Join-Path $PSScriptRoot ".venv\Scripts\tycho.EXE").Replace("\", "/")
+$release = (Join-Path $HOME ".local\bin\tycho.exe").Replace("\", "/")
+
+$text = Get-Content $settings -Raw
+$isLocal = $text.Contains($local)
+$want = $args[0]
+if (-not $want) { $want = if ($isLocal) { "release" } else { "local" } }
+
+switch ($want) {
+  "local"   { $text = $text.Replace($release, $local) }
+  "release" { $text = $text.Replace($local, $release) }
+  default   { Write-Host "arg must be 'local' or 'release'"; exit 1 }
+}
+[System.IO.File]::WriteAllText($settings, $text)  # UTF-8 no BOM (Set-Content -Encoding utf8 adds a BOM in PS 5.1)
+Write-Host "tycho -> $want"