Skip to content

Referee panel, round 2: re-score on current main, referee-majority column, Che4z over LSP, nightly run #4438

Open

Description

@squid-protocol

Follow-up to #4377, whose first measured pass is done (tooling #4384; scorecard in #4377's comment; every engine and key finding fixed: #4302, #4305, #4306, #4391, #4392, #4393).

Remaining

  1. Re-run the panel on current main. The published numbers predate the five engine fixes and the key corrections, so re-score and post the new scorecard.
  2. Add a referee-majority column: engine vs 2-of-3 referees, per fact channel.
  3. Drive Che4z over LSP (documentSymbol + diagnostics) instead of the 2.5.1 analysis CLI, which exits 1 on any program with a CALL and overflows on large ASTs. That cost it about a quarter of the members.
  4. Run nightly, not as a PR gate. JVM start-up plus the 5-minute grammar generation make it a poor PR gate.
  5. Optionally, upstream reports for tree-sitter-cobol-enterprise (CBL/PROCESS cards, ENTRY ... USING, DBCS names) and Cobrix (pic xXXXXX read as 5 bytes).

Policy (unchanged): referees stay test and validation tooling only. They are never vendored, imported by the product or shipped.

🤖 Generated with Claude Code

Activity

  1. added
    enhancementNew feature, sensor, or structural signature
    testingUnit, integration, and E2E pipeline verification
    legacy-modernizationCOBOL refractor, dead-code extraction, and JCL forging
    on Oct 5, 2026
  2. squid-protocol commented on Oct 5, 2026

    @squid-protocol
    OwnerAuthor

    Note 2026-10-05: running the re-score internally is fine, but publishing new comparative results (scorecards or docs pages naming other tools) is on hold pending a review. Post numbers here only once that is cleared.

  3. squid-protocol commented on Oct 18, 2026

    @squid-protocol
    OwnerAuthor

    Item 2 (referee-majority column) is merged in #5409. Items 1 (re-score on main; publishing on hold per owner note 2026-10-05), 3 (Che4z over LSP) and 4 (nightly run) remain, so this stays open.

  4. squid-protocol commented on Oct 23, 2026

    @squid-protocol
    OwnerAuthor

    Churn run 4438-20261023T0152Z (host nyx) ended without a PR. No PR: referees not installed on box, publishing on hold; item 2 already merged in #5409. Handoff at handoffs/churn-4438-handoff.md

  5. squid-protocol commented on Oct 24, 2026

    @squid-protocol
    OwnerAuthor

    Churn run 4438-20261024T2034Z (host melek) ended without a PR. No PR: referee-majority column already in main (#5409); rescore saved in handoff-4438-rescore-20261024.md; publishing on owner hold (2026-10-05); issue stays open

  6. squid-protocol commented on Oct 25, 2026

    @squid-protocol
    OwnerAuthor

    Churn run 4438-20261025T2059Z (host nyx) ended without a PR. No PR: remaining items wait on owner (publishing hold, upstream reports)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature, sensor, or structural signaturelegacy-modernizationCOBOL refractor, dead-code extraction, and JCL forgingpriority: mediumscope:infraCI, tooling, churn/factory, docs infrastructuretestingUnit, integration, and E2E pipeline verification

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions