Repository navigation
v0.7.2 — the scoped check path records its environment
What this fixes
An independent audit of v0.7.0 (never using a client repository) reproduced two
failures. One was a genuine Asha defect, one a git-lifecycle robustness gap.
v0.7.1 shipped the first pass; installing that wheel in a fresh runtime and
re-running the failure case exposed a hole in it, fixed here.
1. comparison_inconclusive:baseline_failures_unparsed — fixed properly
A governed run's baseline check matrix ran under Asha's own interpreter
because the target project had no service-local environment, so pytest aborted
in collection on a missing dependency. Asha correctly refused to pass, but
every cause collapsed into one opaque unparsed detail.
asha.governance.check_diagnosisclassifies each failed check from its own
output:environment_unresolved,missing_dependency,tool_unavailable,
collection_error,test_failures,timeout,crashed,unknown. A
stdlib or repository-local module is a collection error, not a missing
dependency.- Every check entry records
interpreter,hermetic,service_root,
failure_mode,failure_module— on both check paths.run_scoped
builds its own entries next to_run_group, and v0.7.1 decorated only the
latter, so governed runs reported the gap with null identity; both now end in
one_annotate(). - The comparison reports
baseline_missing_dependency(withdiagnosisand an
actionablehintnaming the module, the interpreter and the fix) and refuses
to compute a delta across two different interpreters
(INTERPRETER_MISMATCH).performedstaysfalse. - Acceptance exits
2(interrupted / collection error) and3(internal
error) areinconclusive, notfailed: the runner produced no verdict.
4/5unchanged;1still means the tests ran and failed.
2. fatal: Unable to create '.git/index.lock'
git add -A failed instantly when another git process — usually the worker's
own — held the index, aborting the run before acceptance was evaluated.
git add now waits up to INDEX_LOCK_WAIT_S (3s) for the lock and retries,
then refuses with the lock path and safe recovery instructions. No lock is
ever deleted: Asha cannot prove the owning process is gone. The lock path is
read from the filesystem, so no git subprocess is added to the evidence budget.
Fail-closed rules are unchanged
DONE still requires a demonstrated pass; an inconclusive comparison writes no
seal; every non-passed acceptance outcome still blocks the run.
Verification
- Fresh 0.7.2 runtime, two synthetic repos with their own
.venv:- green repo, real change + passing acceptance →
DONE,COMPARED/
NO_FAILURES, evidence sealed; - repo whose base revision imports an uninstallable module →
FAILED,
comparison_inconclusive:baseline_missing_dependency, hint naming the
module and interpreter, no seal.
- green repo, real change + passing acceptance →
- MCP stdio handshake on the installed wheel:
asha-orchestrator 0.7.2, 14
tools; worker policy active,clean-code4.0.0 preloaded with a matching
SHA-256, non-coding opt-out intact. - CI on the exact release commit:
fail-closed governance gatepass,verify
(full Linux suite, ruff, mypy) pass — 1 failed, 1484 passed, 3 skipped on the
intermediate head, where the only failure was the frozen-trio anchor that the
final commit of this branch advances. - Local Windows suite vs the v0.7.0 baseline: identical failure sets
(33 pre-existing Windows environment failures), zero new failures. - New regression tests:
test_environment_diagnosis.py(including the scoped
path's identity fields),test_index_lock_guard.py,test_mcp_dag_parity.py,
and the acceptance no-verdict cases.
Wheel
asha-0.7.2-py3-none-any.whl
SHA-256 e31562db55e3d69245cea143ace4034494ebae5778d042c4211cfe274c1cc4fe
Docs: docs/ENVIRONMENT-DIAGNOSIS.md.