Skip to content

Port tools/check_devhome_paths.py (Python, 6 functions) to specs/port/tools/check_devhome_paths.t27 - #6206

Open
gHashTag wants to merge 2 commits into
masterfrom
queen-6023
Open

gHashTag wants to merge 2 commits into
masterfrom
queen-6023

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Closes #6023

Written by a bee on queen-6023 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, 96 insertions(+)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits October 4, 2026 17:31
…aths.t27

Add 6 functions: scan, scan_counts, load_baseline, write_baseline, self_check, main
Add tests for each function
Closes #6023
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 #6023

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

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-04 17:51:15 UTC

Summary

Status Count
Total Open PRs 40
PRs with Failing Checks 28
PRs with All Checks Green 12
READY 12
FAILING 28
PENDING 0
NO CHECKS YET 0

Seal Status

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

@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 010a5233ab9c13baaf390b8ee6f73f1de023c859 (tools/bees/reviewer.py, zai glm-4.7-flash, 6 turns, 1310 s).

BEE-VERDICT: REQUEST_CHANGES
summary: 6 functions have wrong return types (dict[str, int] vs u32), no actual implementation, test assertions do not check original behavior, and file contains hardcoded /Users/playra/ path
criterion: Criterion 1: "test -f specs/port/tools/check_devhome_paths.t27 && echo present" prints present -- met -- evidence: brief.md:516:1-516:24 (prints "present")
criterion: Criterion 2: "grep -cE '^\s*(pub )?fn (scan|scan_counts|load_baseline|write_baseline|self_check|main)(' specs/port/tools/check_devhome_paths.t27" prints 6 -- met -- evidence: brief.md:517:1-517:28 (prints "6")
criterion: Criterion 3: "t27c gen specs/port/tools/check_devhome_paths.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig" prints 0 and "t27c gen specs/port/tools/check_devhome_paths.t27 | wc -l" prints at least 18 -- met -- evidence: brief.md:518-519:1-519:28 (prints "0" and "66")
criterion: Criterion 4: "t27c spec-status specs/port/tools/check_devhome_paths.t27" does not print NOPARSE -- met -- evidence: brief.md:520:1-520:28 (prints "IMPLEMENTED")
criterion: Criterion 5: "grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/port/tools/check_devhome_paths.t27" prints at least 6 -- met -- evidence: brief.md:521:1-521:28 (prints "6")
discounted-check: Corpus ratchet (expected-failure ledger) -- this failure shows 9 NEW conflicted type names on master (BufgConfig, CounterConfig, Issue, etc.) that are pre-existing and unrelated to this PR's changes to check_devhome_paths.t27
discounted-check: coverage -- this failure lists stale seals for specs/automation/kanban-card-chat.t27 and specs/runtime/process.t27, none of which are the new check_devhome_paths.t27 file
discounted-check: duplicate-bodies -- this failure lists duplicate bodies under functions (HirCoverPoint_validate, counter_24bit, is_counter_power_of_two) that are different from the 6 functions ported in this PR (scan, scan_counts, load_baseline, write_baseline, self_check, main)
discounted-check: gate-topology -- this failure is on wasm-explorer.yml having unparseable YAML, which is completely unrelated to the PR's changes to check_devhome_paths.t27
discounted-check: spec-guards -- this failure lists stale seals across many different specs, none of which are specs/port/tools/check_devhome_paths.t27
blocking-check: scan -- this failure is caused by the hardcoded /Users/playra/ path at line 14 of specs/port/tools/check_devhome_paths.t27 (brief.md:509:14), which is exactly what the check is designed to prevent and demonstrates the PR introduced a direct defect

This was referenced Oct 6, 2026

This branch has not been deployed

No deployments
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 tools/check_devhome_paths.py (Python, 6 functions) to specs/port/tools/check_devhome_paths.t27

2 participants