statuslisted

You are running `/status` in the **current working directory's repo**. **A repo's rhiza state has two halves, and this reports both:** | half | file | question | | --- | --- | --- | | **config** | `.rhiza/template.yml` + repo structure | is what we'd sync *from* well-formed? | | **sync** | `.rhiza/template.lock` | what was actually synced, and when? | They can disagree in both directions, which is why reporting one without the other misleads: a freshly `/init`-ed repo has a valid config and **no lock at all**, and a long-synced repo can have a lock alongside a config someone has since broken by hand. **This command is a thin wrapper around two bundled scripts** — `plugin/scripts/validate.py` and `plugin/scripts/status.py`, both deterministic and stdlib-only (no `rhiza` CLI, no PyYAML). Do **not** re-implement the parsing or gather fields yourself; run them and relay the output. Purely descriptive: it **reports; it does not score, fix, or file anything**. Argument (optional): `$ARGUMENTS` — a path to the repo root to inspect; default is the current directory. ## 1. Validate the config `${CLAUDE_PLUGIN_ROOT}` resolves at runtime (**keep the quotes**); in a source checkout it's empty, so fall back to the repo-relative path. ```bash uv run --python 3.12 --no-project python "${CLAUDE_PLUGIN_ROOT}/scripts/validate.py" $ARGUMENTS ``` It checks more than the file: that the target is a git repo, that it has the expected language-specific structure (a `pyproject.toml` is requ