Answer prose round 1: 0 🔴, 4 🟡 (0 misread); the entry says what OTLP is and sends, the archive traces each cycle, and both lists keep their order
CI / tests (pull_request) Successful in 3m5s
CI / tests (pull_request) Successful in 3m5s
This commit was merged in pull request #563.
This commit is contained in:
+5
-5
@@ -13,8 +13,8 @@ Each project principle states one rule that the decisions below apply; their ent
|
||||
# Decisions no project principle covers
|
||||
|
||||
- bin/: a test parametrizes its cases with `subTest`, since pytest's `parametrize` doesn't reach a unittest `TestCase`
|
||||
- bin/: the tools send no OTLP traces, logs or metrics, and loop-claude's archive is the trace of each cycle
|
||||
- bin/: the tools run on the host's Python, with no container, and so do their tests outside CI
|
||||
- bin/: the tools send no OTLP traces, logs or metrics, and loop-claude's archive holds the trace of each cycle
|
||||
- bin/: the tools support only the latest stable Python, and the tests, written in plain unittest, run on it in four pytest-xdist workers
|
||||
- chunk-pr: the chunks of a project merge one at a time on a machine, each finishing its plan items in its turn, and a pull request that waits for an approval leaves the queue while it waits
|
||||
- deploy: this repo keeps no `AGENTS.md`, since `~/.claude` is its checkout; its principles and decision titles head `docs/decisions.md`, its working rules follow them there, and its `.claude/settings.json` excludes every `.claude/CLAUDE.md`, so a session in the clone loads only the clone's `CLAUDE.md`
|
||||
@@ -72,14 +72,14 @@ Settling a call is the human's. The chunk that settles the calls cites, in `docs
|
||||
|
||||
Valid while the archive's file names, the Vocabulary and the panel keep these words.
|
||||
|
||||
## bin/: the tools send no OTLP traces, logs or metrics, and loop-claude's archive is the trace of each cycle
|
||||
|
||||
2026-11-16, lilleman, from the release review of 0.11.0. Departs from `principles/technical-principles.md` → "All critical flows should have good traces", whose sub-bullet asks for traceparent OTLP. lilleman ruled that this repo leaves no OTLP traces at all, for good, so no plan item ends this departure. Serves goal 4: the tools run on the human's own machines, beside client code and transcripts, and an exporter would send what they see to a collector. Each critical flow still has its trace, in loop-claude's archive: each cycle's transcripts and its `.outcomes.md` entry, from the chunk's start to its verdict. Valid while goal 4 holds.
|
||||
|
||||
## bin/: the tools run on the host's Python, with no container, and so do their tests outside CI
|
||||
|
||||
2026-09-24, larv-review. Serves goals 1 and 2. The tools drive the host's claude CLI and read the host's session files, which a container cannot see; the tests run on the same host Python the tools meet. The tests also run in a container through `ci.sh`, on CI and to reproduce a CI failure, since they drive no claude (the entry `tests: CI runs the suite through ci.sh`). Valid while claude runs on the host.
|
||||
|
||||
## bin/: the tools send no OTLP traces, logs or metrics, and loop-claude's archive holds the trace of each cycle
|
||||
|
||||
2026-11-16, lilleman, from the release review of 0.11.0. The tools send no traces, logs or metrics over OTLP, the OpenTelemetry protocol, to any collector. That departs from `principles/technical-principles.md` → "All critical flows should have good traces", whose sub-bullet asks for traceparent OTLP. lilleman ruled the departure permanent, so no plan item ends it. Serves goal 4: the tools run on the human's own machines, beside client code and transcripts, and whatever goes to a collector leaves the machine. loop-claude's archive holds the trace of each cycle instead: its transcripts and its `.outcomes.md` entry, from the worker's first run to the judge's verdict. Valid while goal 4 holds.
|
||||
|
||||
## bin/: the tools support only the latest stable Python, and the tests, written in plain unittest, run on it in four pytest-xdist workers
|
||||
|
||||
2026-10-28, lilleman, through todo item 245. Serves goal 1.5: the suite gates every chunk. The suite took 198 s, 102 s of which went to rerunning it on the oldest Python README Install named, 3.11. README Install now asks for the latest stable Python as `python3`, and mypy checks every tool under `bin/` for the version Install names. README's Test line runs the tests in four pytest-xdist workers through `uvx`: 29 s on a 16-CPU machine. Four is one heavy slot's CPUs, `CPUS_PER_SLOT` in `bin/machine_load/slots.py`, so a gate under `run-heavy` loads only the slot it waits for. The line pins pytest and pytest-xdist, as `test_types.py` pins mypy, so every machine runs the gate the same way. It passes the path of `python3`, since `uvx --python python3` picks a Python uv installed itself, which may be older. The tests use stdlib `unittest` alone, and pytest only runs them, so plain `python3 -m unittest` runs the same tests one at a time and another runner can replace pytest. Valid while every machine taking the checkout gets the latest stable Python soon after its release.
|
||||
|
||||
Reference in New Issue
Block a user