Skip to content

Port gHashTag/trinity:src/phi-engine/vibeec_original/tnc.zig (Zig, 1 function) to specs/port/trinity/src/phi-engine/vibe - #7141

Merged
gHashTag merged 2 commits into
masterfrom
queen-5646
Oct 7, 2026
Merged

gHashTag merged 2 commits into
masterfrom
queen-5646

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Closes #5646

Written by a bee on queen-5646 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

1 file changed, 102 insertions(+)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits October 3, 2026 00:15
- Port main() function from src/phi-engine/vibeec_original/tnc.zig
- Add comprehensive tests covering argument validation, file extension checking, and character validation
- Port the decision logic while abstracting file I/O operations
- Generated code compiles successfully with all tests passing

Closes #5646
A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #5646

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

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 22:31:32 UTC

Summary

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

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b23641f01baa != 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).

This was referenced Oct 6, 2026
This was referenced Oct 6, 2026

@t27-bees t27-bees Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer bee verdict for head 148ad22ec7c37147b90b27f9697fb91ebe6f054d (tools/bees/reviewer.py, zai glm-4.7-flash, glm-4.5-flash, 5 turns, 148 s).

BEE-VERDICT: REQUEST_CHANGES
summary: Port meets all acceptance criteria but fails gen-verilog generation
criterion: "1. test -f specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 && echo present prints present" -- met -- evidence: brief.md:534
criterion: "2. grep -cE '^\s*(pub )?fn (main)\(' specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 prints 1" -- met -- evidence: brief.md:535
criterion: "3. t27c gen specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig prints 0, and t27c gen specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 | wc -l prints more than 12" -- met -- evidence: brief.md:536-537
criterion: "4. t27c spec-status specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 does not print NOPARSE" -- met -- evidence: brief.md:538
criterion: "5. grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 prints at least 1" -- met -- evidence: brief.md:539
criterion: "6. t27c test-report specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 2>&1 | grep -c BLOCKED prints 0" -- met -- evidence: brief.md:540
discounted-check: spec-guards -- Drift in corpus statistics appears systemic, not specific to this port (3 figures drifted, no mention of this file)
discounted-check: t27b-native-ratchet -- No specific details provided to link this failure to the new file
blocking-check: Corpus ratchet (expected-failure ledger) -- The new file causes unexpected gen-verilog failure, breaking corpus expectations for multi-backend support

Evidence

Let me analyze this pull request against issue #5646:

Acceptance Criteria Analysis

All 6 acceptance criteria from the issue were verified and passed:

  1. ✅ File existence: The file specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 exists and prints "present"
  2. ✅ Function count: Contains exactly 1 pub fn main() function as required
  3. ✅ Generation quality: Generated Zig code has 0 "not yet implemented" placeholders and 78 lines (more than the required 12)
  4. ✅ Parse status: File parses successfully (status: IMPLEMENTED)
  5. ✅ Test coverage: Contains 8 test blocks (more than the required 1)
  6. ✅ Compilation and tests: Generated code compiles and runs tests with 0 BLOCKED results

The port correctly follows the issue requirements:

  • Ports the decision logic, not the plumbing (file I/O is mocked as undefined)
  • Tests assert on the behavior the original would have
  • Only contains the specified functions with the correct names
  • Stays within the boundary (only one file changed)

Red Checks Analysis

Corpus ratchet (expected-failure ledger) - BLOCKING

  • Issue: The new file causes an unexpected failure in the gen-verilog backend: + specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27 [gen-verilog]
  • Why it blocks: This is a real defect introduced by the PR. The T27 system specs must work across all backends (gen, gen-c, gen-verilog). The file's string manipulation and path checking logic doesn't translate to hardware description language (Verilog).

spec-guards - DISCOUNTED

  • Reason: Shows general corpus drift (3 figures drifted) but no specific connection to this port. This appears to be systemic drift in corpus statistics, not caused by this specific change.

t27b-native-ratchet - DISCOUNTED

  • Reason: No specific details about what failed. Cannot establish that this is related to the new file rather than general master instability.

Verdict

The change successfully meets all acceptance criteria for issue #5646 - it properly ports the Zig function to .t27 format with adequate tests and generates working code for Zig and C backends. However, the gen-verilog failure is a legitimate blocking defect because:

  1. The roadmap stage specifically targets "t27c gen (Zig), gen-c" but the system expects all specs to work across all backends
  2. The corpus ratchet tracks which specs work with each backend, and this new spec breaks that
  3. The file's string and path manipulation logic is fundamentally software-oriented and doesn't map well to hardware description

@gHashTag
gHashTag enabled auto-merge (squash) October 7, 2026 07:22
@gHashTag
gHashTag merged commit d576295 into master Oct 7, 2026
26 of 29 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.

Port gHashTag/trinity:src/phi-engine/vibeec_original/tnc.zig (Zig, 1 function) to specs/port/trinity/src/phi-engine/vibeec_original/tnc.t27

2 participants