Skip to content

[Tracking] Verify and integrate ScaleAI and mvanhorn PR queues #6262

Closed

Description

@gensokyo-dev

Current outcome — complete (2026-10-22 UTC)

The original 12-PR inventory and the two later mvanhorn additions are all merged. The final requested five:

PR Contributor Actual merge Merged at
#6169 earakely-scale 5375ff0f9 2026-10-22T15:46:53Z
#6136 earakely-scale 7ec9b6e56 2026-10-22T15:57:36Z
#6138 earakely-scale 957bcfa14 2026-10-22T16:12:27Z
#6268 mvanhorn 5d7d6ad9a 2026-10-22T14:22:23Z
#6273 mvanhorn 3d472bde2 2026-10-22T15:00:52Z

Late #6136 UUID findings were tracked in #6343 and fixed by #6345, merged as 54f51f0d7dc9c48355928a3d9ec84e6fc13e8e54. Its four new integration guards fail before/pass after; exact-head verification passed 763 related source tests, 20 compiled CLI/MCP serving/schema boundaries, full static/docs/discovery checks and five immutable public capture workflows. Independent Codex source review and final-head Greptile review reported no new actionable findings. Actual merge rebuilt: all 12 selected source/CLI/MCP tests and all five public capture workflows passed again, with unchanged Evidence IDs versus the reviewed candidate.

Performance, failure attempts, exact scope and limitations are in the individual PRs. Public recordings are not live-app write qualification; real-provider/platform gaps remain explicit. Authorized bypass was used where CI/metadata gates were incomplete; unfinished CI is not reported as passed, and no human-review attestation was fabricated. The five final feature merges preserve the original contributor as primary author and contain no Co-authored-by trailers.

The historical inventory/progress below records contemporaneous observations; old draft/queue descriptions are not current status.


Requested outcome

Review, verify and integrate the outstanding contributions from earakely-scale and mvanhorn, one PR at a time, preserving contributor history. This is a coordination record, not approval of unverified code or capability scope.

Queue observed on 2026-10-22

Author PR Outcome Initial triage
mvanhorn #4837 ELF PT_NOTE/SHT_NOTE inspection First verification candidate; no unresolved review threads; latest-main integration is clean. Prior CI failures concern setup JVM cleanup and browser deadline termination, not the ELF files.
mvanhorn #4830 PE certificate-table inspection Three unresolved threads; inspect failing checks before deciding attribution.
mvanhorn #4826 CPython pyc/marshal inspection Author actively updating; CI/review pending. Avoid overwriting intervening commits.
mvanhorn #2331 Byte entropy profiles Conflicts with main; isolate the feature rather than replaying unrelated changes.
mvanhorn #4833 Erlang BEAM chunks/tables Conflicting, 998-file diff at initial triage; investigate ancestry and recover only intended changes.
earakely-scale #5600 Evidence-gated environment state writes Base for the remaining stack; author actively updating, CI running.
earakely-scale #5699 Compare environment fidelity to probe captures Stacked on #5600; conflicts; four unresolved threads.
earakely-scale #5787 Whole-line list membership Stacked on #5600; two unresolved threads.
earakely-scale #5800 List filter/search/sort/paging queries Stacked on #5787; five unresolved threads.
earakely-scale #6136 Renamed/regenerated write values Stacked on #5600; draft, independent of #6138.
earakely-scale #6138 View-specific clock spelling Stacked on #5600; draft, independent of #6136.
earakely-scale #6169 Bodiless replies, omitted/projected fields and digit-group sequences Stacked on #5600; four unresolved threads.

These are point-in-time API observations, not completed diagnoses. Thread and CI counts may change. #5351/#5352 are earlier dependencies mentioned in the Scale branch descriptions; verify their integration before restacking.

Integration protocol

  • Fetch current main before each worktree/branch; keep original user files untouched.
  • Preserve the author's commits and intervening pushes; prefer ordinary merges, and use focused cherry-picks/replacement PRs only when ancestry or conflicts justify them.
  • Check the actual owning representation and affected consumers, not only regression assertions. CLI/MCP must share contracts and Evidence semantics.
  • Run focused tests and real public workflows with independent oracles where applicable. Record toolchain, exact revision, provenance, costs and unverified coverage. Bound local concurrency and memory.
  • Address attributable findings. Record unrelated failing checks rather than silently claiming them fixed or weakening tests.
  • Merge only after appropriate verification/review. Preserve truthful human declarations; do not invent human review or add Co-authored-by trailers in maintainer follow-ups.

Executed progress

Activity

  1. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    Queue update: #5600 was merged by another maintainer as 538017d at 2026-10-22T06:15:36Z; I did not perform that merge. The remaining Scale branches are being restacked by their author and their earlier review threads have been resolved. For #4837, I preserved author update 64b9dbc and used expected-head ordinary update-branch to incorporate current main (a77143e). Exact tree comparison exposed three dropped Windows curated test paths; the existing guard failed before (1 failure / 9 passes), and morluto has supplied d4fbca9 restoring them. Verification follows that exact head, with no duplicate fix or force-push. Earlier real readelf-backed CLI/MCP and actual Codex checks passed; exact-head retests/CI are still pending.

  2. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    Queue refresh (2026-10-22): #4830 was merged by @morluto as ca4ca65 at 09:20:08 UTC, including the author’s certificate text fixes; #4833 was merged by @morluto as bfba998 at 09:46:16 UTC. I did not perform those merges. The obsolete in-progress PE integration worktree is preserved and will not be pushed over the newer work. Current packet: #5787 (before dependent #5800), fresh main 3a42a9e plus contributor 0499ed1. Reproduced the mixed-line empty offset=2/data-add regression with a valid fixture: expected an empty later page, observed the newly loaded earlier entity. A producer-owned paging admission fix and deterministic control/alias tests now pass (61 source tests); broader/public verification is in progress. Ignored write-query values, encoded create-observation matching, and fallback-absence ordering also exist in main’s unchanged code and are being explicitly attributed rather than claimed fixed here.

  3. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    #5787 review attribution update: the PR API was still pinned to base 538017d and showed 332 files, although the real delta against current main was 18. Reapplying base=main refreshed the owning GitHub metadata to 932fbb7; both PR files and main...head comparison now show 18 files, with unchanged reviewed head 36571c4. The latest Greptile finding concerns NativeExportParser.ts (PE name/version string allocation before shared allowance); that file is byte-identical to already-merged main 3a42a9e and absent from the actual PR delta. Record this as a separate source-derived main candidate, not a #5787 defect or a reproduced OOM. No large hostile-input run was attempted, and no runtime memory reproduction or fix is claimed. Actual 932fbb7+36571c494 integration tree f9adc9a9dae1f7f771965e48f77ad61aaad5a65e was built and passed the real retained-data CLI/MCP/load/reset workflow (10.09 s wall, 15.79 s CPU, 496.78 MiB sampled process-family RSS).

  4. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    #5787 merged normally (no bypass) by gensokyo-dev as 4043e71 at 10:34:56 UTC. Primary author earakely-scale retained; no Co-authored-by. All technical CI and readiness/title checks passed; exact-head Greptile completed, with its sole new finding attributed to unchanged main code after correcting stale PR base metadata. Entire actual-merge tree equals the pretested latest-main integration tree. Rebuild, 491 source tests, and the real retained-data CLI/MCP/data-add/paging/reset workflow passed again. Evidence/costs/failed grader/coverage limits: #5787 (comment). Six original queue entries remain; next packet is mvanhorn #4826 before continuing the remaining Scale stack.

  5. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    Current packet: #5800, contributor head 30e90fc normally advanced to 665ec74 on fresh main 2c3dd94; original PR/fork/history retained, no Co-authored-by. Preserved main ownership/paging safeguards and repaired the three attributable review findings plus ambiguous page-base inference. 618 adjacent source tests, 80 CLI/MCP/schema boundary tests, three 99-test stability runs, pinned static/docs/build checks, native held-out GitHub pagination and three actual Codex sessions passed. The initial candidate still made an unnecessary full-list call; a 33-byte catalog clarification led to one call with the unchanged prompt in the next session. All traces and limitations are preserved, not a universal speedup claim. Current evidence: https://github.com/morluto/rea/blob/665ec74c6ed57947e06f72bed53138a171a9bc50/docs/specs/agent-environments/list-queries/verification.md . CI run 39773075218 and fresh Greptile review are in progress, not yet a merge or full-CI success. Independently attributed unchanged-main findings: later-create response constants (source blob 420a1ad18e970491f7d6059dbbe8960a48d989e7) and ignored write-query modes; no runtime reproduction or fix claimed here. Original queue still has five open Scale PRs until this packet merges. Two additional open mvanhorn PRs #6268/#6273 remain a separate later packet.

  6. gensokyo-dev commented on Oct 22, 2026

    @gensokyo-dev
    CollaboratorAuthor

    Final #5800 candidate is 62a9adf, current main e93e3b1 (APK signing preserved), actual 28-file delta. Independent review exposed an additional total-omission defect; representation cross-check also reproduced a stale canonical string total. Both now have fail-before/pass-after guards and owner-level fixes. 621 source tests, three 102-test stability runs, 36 final compiled service/schema boundaries, static/build/docs/format and native held-out pagination pass. Two targeted Codex re-reviews find no definite remaining defect (source review only). Fair latest-base serial public workflow: control 10.07s wall/15.67s CPU/490.34MiB sampled family RSS, candidate 10.04s/15.48s/498.06MiB. Earlier slower sample retained; no speedup attribution. Replies 13282→1383 bytes, catalog 1057→1090, supported completed query two→one calls. Final CI 39776472358 and Greptile 119816576430 still pending, not yet merged; no older green CI substituted. Raw prompts/traces/failed checks/costs preserved locally, current limitations in PR body and verification doc.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions