8000 docs: the README suite count is the Makefile's (test); OVERVIEW names the new tools by adeelahmad · Pull Request #36 · adeelahmad/aloop · GitHub
[go: up one dir, main page]

Skip to content

docs: the README suite count is the Makefile's (test); OVERVIEW names the new tools - #36

Merged
adeelahmad merged 1 commit into
masterfrom
claude/project-thread-qerfr9
Oct 18, 2026
Merged

adeelahmad merged 1 commit into
masterfrom
claude/project-thread-qerfr9

Conversation

@adeelahmad
Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Before: the README said make ci runs "30 Python/Node suites" while the Makefile runs 43, and nothing caught the drift. OVERVIEW's harness-tools row did not name intent-trigger (#34) or run-summary (#35), and quoted 58 conformance checks where there are 60. ROADMAP M8 listed "measured public runs on Codex and OpenCode" as open without saying what blocks it.

After: the README quotes 43 and readme.test.py derives that number from the Makefile, so the next added suite without a README update fails CI. OVERVIEW names both new tools and the right conformance count. M8 records that the Codex/OpenCode runs need an owner machine with both CLIs, since this environment has neither and an unmeasured number is not published.

How: a sixth check in scripts/test/readme.test.py (red at 30, green at 43) plus the three doc edits. make ci: 60/60.


Generated by Claude Code

… the new tools

CLAUDE.md "done means" OVERVIEW and ROADMAP match the code. The README quoted "30
Python/Node suites" while the Makefile runs 43; readme.test.py now derives the count
from the Makefile and fails on drift. OVERVIEW's harness-tools row names intent-trigger
and run-summary and its conformance count is 60 (was 58). ROADMAP M8 records why the
Codex/OpenCode measured runs stay open (no codex/opencode CLI in this environment).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QxyVf3NgwsgRyYpBgDDTC
@adeelahmad
adeelahmad merged commit 9e653da into master Oct 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0