Skip to content

databases/Frontier.root is stale (pre-#621, doubled-brace corruption); source of #866 false diagnosis #877

Open

Description

@jsavin

Rationale

databases/Frontier.root is STALE and ships pre-#621 doubled-brace script corruption. Untouched since PR #594, its system.startup.startupScript does NOT compile as-shipped (carries pre-#621 damage signature: comment nodes with 0 proper 0xC7 markers, 74 literal "//", 61 ";;"). Virgin.root's copy is clean. The stale Frontier.root is almost certainly the source of the misleading "opcode-0" report in #866's original text (the false root-cause about codegen defects). ~13 test/tool scripts reference it (run_headless_tests.sh checks its v7 magic; bisect and CLI tests use it).

Current State

Stale copy identified (2026-08-10):

References to stale copy:

  • run_headless_tests.sh checks v7 magic number on Frontier.root
  • bisect tests use it
  • CLI tests reference it
  • ~13 test/tool scripts depend on it

Impact:

Desired Outcome

Refresh databases/Frontier.root to current state:

  1. Rebuild from Virgin.root (make dist does this for dist/ — apply same to checked-in copy)
  2. OR re-evaluate whether checked-in copy should exist (CLAUDE.md says edits are local-only anyway)
  3. Verify: all scripts in Frontier.root compile and match Virgin.root post-langstripstructuremarkers + oplangtextvisit round-trip drops a closing brace on multi-level outlines #621 state

Recommendation

Option A (recommended):

  • Run: make clean && make dist (rebuilds dist/Frontier.root)
  • Copy to databases/Frontier.root: cp dist/Frontier.root databases/Frontier.root
  • Commit the refreshed copy
  • Verify: run_headless_tests.sh passes with new copy

Option B (structural):

  • Remove checked-in databases/Frontier.root from repo
  • Rebuild from Virgin.root at test time (make dist step)
  • Update tests to use dist/Frontier.root or rebuild on the fly
  • Rationale: CLAUDE.md says local edits only; checked-in copy is not the source of truth

Exit Criteria

Related Context

Activity

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

    priority/p1High priority - address soonscope/quick-win< 4 hours, obvious solutiontype/bugDefect in existing functionality, needs fixworkstream/database-architectureDatabase format, migration, serialization

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions