Skip to content

spec(t27os): receipt_result.t27 -- the lab.yml writer step for the typed result section (Refs #11954) - #12113

Merged
gHashTag merged 1 commit into
masterfrom
night/18-result-writer
Oct 24, 2026
Merged

gHashTag merged 1 commit into
masterfrom
night/18-result-writer

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Refs #11954 (board Trinity-S-AI-DNA/t27os#18, criterion 2).

specs/t27os/receipt_result.t27 gains RESULT_STEP_YAML: the lab.yml step text that goes between "write the receipt" and "publish the receipt" and appends the typed result section:

  • reads the same /tmp/out/summary.txt the display rows come from, strips each key= prefix;
  • a row is reported only when all five counts are integers -- a spec whose test-report printed NA is not reported, so reported < asked and ok is false (the t27os#9 omission rule, not a new rule);
  • ok starts false and is set only by the conjunction asked > 0, reported == asked, bad + fail + vacuous + blocked == 0 -- result_ok in shell, a row that does not add up counting as bad;
  • appended by dropping the receipt's closing brace, so it also follows a merged die witness; no interpreter, no awk.

Three new tests pin each clause, refuse an interpreter in the step, and tie the NA rule to the existing omission verdict.

Lab: run 40136220581 (seal=true), receipt to land at runs/fd0ee966b3d25ea495baaece5c0e5074e74877f3.*.json in Trinity-S-AI-DNA/t27os. Draft until the receipt is in.

Next: the step text placed into Trinity-S-AI-DNA/t27os lab.yml; then criterion 3 (a consumer branching on result.ok).

🤖 Generated with Claude Code

…ped result section, pinned by tests (Refs #11954)

RESULT_STEP_YAML is the step text lab.yml places between 'write the receipt' and
'publish the receipt': integer rows from /tmp/out/summary.txt, a row with a non-integer
count is not reported (the t27os#9 omission rule), ok = result_ok in shell. Board
Trinity-S-AI-DNA/t27os#18 criterion 2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-24 21:54:27 UTC

Summary

Status Count
Total Open PRs 45
PRs with Failing Checks 40
PRs with All Checks Green 5
READY 4
FAILING 40
PENDING 0
NO CHECKS YET 0

These columns do not partition: 4 + 40 + 0 + 0 = 44, and there are 45 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=55c0f1b1b32d != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag

Copy link
Copy Markdown
Collaborator Author

Lab receipt (run 40136220581, seal=true): Trinity-S-AI-DNA/t27os runs/fd0ee966b3d25ea495baaece5c0e5074e74877f3.803d4cf9.json

  • t27c: specs/t27os/receipt_result.t27|tests=10|pass=10|FAIL=0|vacuous=0|blocked=0
  • t27b: specs/t27os/receipt_result.t27|leg=t27b|tests=10|pass=10|FAIL=0|vacuous=0|asserts=35
  • seal leg: 0 drifted (the module carries no seal)

@tri-claw

tri-claw Bot commented Oct 24, 2026

Copy link
Copy Markdown

Summary by t27-bees

Checked by the t27 compiler

t27c parse, parse-complete and typecheck on each changed .t27 file at fd0ee96. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/t27os/receipt_result.t27: parses and typechecks.

Read by the model

Worth a look

  • specs/t27os/receipt_result.t27 (the printf '{"spec": "%s", ...}' "$spec" in RESULT_STEP_YAML): The spec name is interpolated directly into JSON without escaping. If a spec name contains ", \, or control characters, the generated receipt becomes invalid JSON and downstream consumers will fail to parse it.

  • specs/t27os/receipt_result.t27 (the sed -i '$d' "$file" in RESULT_STEP_YAML): This deletes the last line of the receipt file assuming it is exactly a lone }. If the receipt is minified, pretty-printed with trailing whitespace, or has a newline after the brace, the wrong line is removed and the appended result section produces malformed JSON.

  • specs/t27os/receipt_result.t27 (the git ls-files -o … | head -1 in RESULT_STEP_YAML): Picks the first untracked runs/$sha.*.json file. If multiple receipt files exist for the same SHA (e.g., from parallel matrix legs), the step types the wrong one silently.


Read: 1 files, +55 -2, the whole diff. Head fd0ee96. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@gHashTag

Copy link
Copy Markdown
Collaborator Author

Night tick 132: the step text from this PR, placed in Trinity-S-AI-DNA/t27os#34, wrote its first typed result section: runs/41c281458b90981dffa649493f368d27667bfa55.e88ac91e.json in Trinity-S-AI-DNA/t27os, ok=true asked=2 reported=2 (branch-ref run 40137152684, t27c + t27b jobs success).

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.

1 participant