Skip to content

The gate I added could never have run, and enum was not the only key the converter drops - #6798

Merged
gHashTag merged 4 commits into
masterfrom
queen-5275
Oct 22, 2026
Merged

gHashTag merged 4 commits into
masterfrom
queen-5275

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Collaborator

Closes #5275

Written by a bee on queen-5275 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.

4 files changed, 323 insertions(+), 33 deletions(-)

🤖 Generated with Claude Code

Trinity Bee and others added 3 commits October 6, 2026 02:54
…per functions

- Add LANG_T27, LANG_ZIG, LANG_PYTHON, LANG_C, LANG_RUST, LANG_VERILOG constants
- Add language ID helper functions (language_id_from_extension, is_*_extension)
- Add comprehensive tests for all constants and functions
- Remove TODO: Implement stub body
- All 27 tests pass, meeting acceptance criteria

Closes #5275
The turn ended with these files edited and never committed. Uncommitted
work is invisible to the review - it reads the branch - so the attempt
would have been released as empty and the next bee would have started
beside this work rather than from it.

This commit is not a claim that the work is correct. It is the bee's
work, committed on its behalf, and it is judged exactly like any other:
the adversarial reviewer reads it, the compiler runs on it, and the
issue's own criteria are measured against it.

Issue: #5275
Turn: 8fcb07cd-9409-4f9e-b168-11a96b5f3de8
Ending: finished (the turn closed)
Committed: 3 path(s)
Left uncommitted: 0 path(s) outside the declared boundary
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 #5275

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 12:43:29 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 44
PRs with All Checks Green 6
READY 1
FAILING 44
PENDING 0
NO CHECKS YET 0

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

Seal Status

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

gHashTag commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator Author

This branch conflicts with master on .trinity/seals/lsp-language.json, .trinity/seals/lsp_Specs.Lsp.Language.json, .trinity/seals/lsp_lsp-language.json, specs/lsp/language.t27, a real content conflict that GitHub's update-branch cannot resolve (checked with git merge-tree against master at 2026-10-07 ~16:10Z). It is left open for conflict_step (#7571), which redoes it from fresh master once the wiring (#7573) lands.

@gHashTag
gHashTag enabled auto-merge (squash) October 11, 2026 12:56
@gHashTag
gHashTag disabled auto-merge October 11, 2026 13:02
@gHashTag
gHashTag enabled auto-merge (squash) October 12, 2026 10:42
@gHashTag
gHashTag disabled auto-merge October 12, 2026 10:46
@gHashTag
gHashTag enabled auto-merge (squash) October 22, 2026 15:58
# Conflicts:
#	.trinity/seals/lsp-language.json
#	.trinity/seals/lsp_Specs.Lsp.Language.json
#	.trinity/seals/lsp_lsp-language.json
#	specs/lsp/language.t27
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-22 19:41:00 UTC

Summary

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

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

Seal Status

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

@tri-claw

tri-claw Bot commented Oct 22, 2026

Copy link
Copy Markdown

Summary by t27-bees

This pull request adds three seal files (build verification artifacts) and a publication notice documenting work on issue #5275. The seal files record successful test results (27 passed) for the lsp-language module across multiple target languages. The actual spec change to specs/lsp/language.t27 is referenced but not shown in the provided diff.

Worth a look

  • Nothing stood out. The diff shows only generated seal artifacts and a documentation entry; no source code logic is visible to review for correctness.

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

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.

The gate I added could never have run, and enum was not the only key the converter drops

2 participants