Skip to content

Tidy repository structure: root docs, dead pipeline, fork doc copies, README/Makefile - #415

Merged
rebelice merged 6 commits into
mainfrom
claude/omni-structure-cleanup-a69ae7
Sep 14, 2026
Merged

rebelice merged 6 commits into
mainfrom
claude/omni-structure-cleanup-a69ae7

Conversation

@rebelice

Copy link
Copy Markdown
Collaborator

Summary

Structure-only cleanup. No parser, catalog, or test logic changes; the single non-comment Go change is the prompt path in scripts/dashboard.go.

Area Change
Repo root 26 SCENARIOS-*/EXECUTION-*/STARMAP-* docs moved to docs/scenarios/<engine>/. PG_SEMANTIC_INVENTORY.json, metrics.db, four .skill zips deleted. Root now holds only go.mod, Makefile, README.md, LICENSE, tools.go and the engine directories.
docs/ docs/superpowers/{plans,specs} (75 files, same format as docs/plans) merged into docs/plans/ and new docs/specs/. Go comments and cross-references updated.
Dead pipeline The March-2026 pg-semantic Python pipeline deleted in full: scripts/pg-semantic/, its driver/metrics scripts, pg/semantic, redshift/semantic, mariadb/semantic, .gemini/skills, the four self-declared-deprecated scripts/pg-*-skill/ dirs, docs/pg-semantic-pipeline-migration.md, pg/catalog/PROGRESS.json. Nothing in Go or CI referenced any of it.
Tracked junk Removed __pycache__, pg/catalog/logs/*.log (agent session logs with local paths), and `mysql
scripts/ Agent prompts moved to scripts/prompts/; driver.sh, dashboard.go, extract-bnf.sh follow. Hardcoded /Users/rebeliceyang/... paths in prompts and parser SKILL.md files replaced with <repo root>. stream-filter.py loses its hook into the deleted metrics.py.
Fork copies redshift (fork of pg) and mariadb/tidb (forks of mysql) carried byte-identical copies of the parent's PROGRESS.json, SKILL.md, SCENARIOS-*.md, scenarios_bug_queue/. Deleted; test comments now point at the parent's file. Files a Go test actually opens (PAREN_AUDIT*, PARSER_DISPATCH_AUDIT.md, SPLIT_COVERAGE.json, compat/report.md, BNF catalogs) stay. redshift/README.md rewritten (it was pg's README verbatim).
README / Makefile Status table covers all 17 engines and their packages (it listed four and called the MySQL catalog "Planned"). Makefile generates test-<engine> for every engine and adds test-short.

Net: 403 files, +577 / −27,324 lines.

Not done on purpose

  • docs/plans/ historical plans keep their references to now-deleted paths; they are records of the time.
  • Six Go files report gofmt -l but were already unformatted on main; left alone.
  • Per-engine internal layout differences (root package or not, analysis vs semantic naming) are out of scope.

Test plan

  • go build ./...
  • go test -short ./... (the CI suite) passes
  • Targeted: pg/parser and redshift/parser PAREN lint tests, redshift/compat, pg/splittest, mysql|mariadb|tidb/parser -run TestVerify, mysql|mariadb/validate
  • Sweep for dangling references to every deleted path (only historical docs/plans mentions remain)

🤖 Generated with Claude Code

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-14T03:08:11.667494Z 2f7d109 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 700b1b2deb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Makefile Outdated
Comment thread README.md Outdated
rebelice and others added 4 commits September 14, 2026 02:39
…wers into docs/plans and docs/specs

The repo root carried 26 SCENARIOS/EXECUTION/STARMAP checklists that no
code or CI reads. They now live in docs/scenarios/<engine>/. The two
scenario docs under mysql/semantic (a non-Go directory) move there too.

docs/superpowers/{plans,specs} held 75 dated files in the same format as
docs/plans, produced by a different tool. They are merged into
docs/plans and a new docs/specs; Go comments and cross-references are
updated. The quality corpora's `-- @source:` comments and
engine-capability-guide now point at the new paths.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…k, move prompts to scripts/prompts

The March-2026 pg-semantic Python pipeline (scripts/pg-semantic, its
driver/metrics scripts, the */semantic artifact directories, the
.gemini skills, the root PG_SEMANTIC_INVENTORY.json, metrics.db and
the four .skill zips) has not been touched since 2026-03-21 and nothing
in Go or CI reads it. The four scripts/pg-*-skill directories already
declared themselves deprecated. pg/catalog/PROGRESS.json pointed at the
deleted pipeline as its replacement.

Also removes files that were tracked despite matching .gitignore
(parser/{driver,status}.sh) or that are session output
(pg/catalog/logs/*.log, __pycache__), and extends .gitignore so they
cannot come back.

Agent prompt templates move from scripts/ to scripts/prompts/; driver.sh,
dashboard.go and extract-bnf.sh follow. Hardcoded /Users/... paths in
the prompts and parser SKILL.md files become `<repo root>`.
stream-filter.py drops its optional hook into the deleted metrics.py.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…pg and mysql

redshift was forked from pg and mariadb/tidb from mysql with every
PROGRESS.json, SKILL.md, SCENARIOS-*.md and scenarios_bug_queue file
copied along. The copies were byte-identical to the originals and
nothing read them. Test comments now point at the parent engine's
file. Files that a Go test actually opens (PAREN_AUDIT*,
PARSER_DISPATCH_AUDIT.md, SPLIT_COVERAGE.json, compat/report.md, BNF
catalogs) stay. redshift/README.md, previously a copy of pg's, now
describes the Redshift package.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The status table listed four engines and still called the MySQL catalog
"Planned". It now lists every engine with its packages, and the layout
tree matches the reorganised docs/ and scripts/. The Makefile generates
a test-<engine> target per engine and adds test-short, the CI suite.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@rebelice
rebelice force-pushed the claude/omni-structure-cleanup-a69ae7 branch from 700b1b2 to f6c98f7 Compare September 14, 2026 02:41
…e module from make test

Review follow-ups. The README claimed every root package exposes Parse;
partiql only exports Split and elasticsearch exports
ParseElasticsearchREST, so the entry points are now listed per engine.
`make test` also runs harness/conformance, a nested module ./... does
not reach, to match CI. The spanner harness fails without a live
emulator, so it gets its own test-spanner target instead.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@rebelice

Copy link
Copy Markdown
Collaborator Author

Rebased onto main (8 new commits, including #422 dropping testing.Short()).

  • Conflicts were limited to Makefile and mariadb/semantic/SCENARIOS-deparse.md. Makefile now carries main's proto-breaking target and the removal of test-mysql-quick; the test-short target this PR had added is gone along with -short. The mariadb doc was a byte-identical copy and stays deleted; main's one-line edit to it is present in the moved docs/scenarios/mysql/SCENARIOS-mysql-deparse.md.
  • Verified: the set of changed files is identical before and after the rebase; in the 52 test files both sides touched, this PR's changes are comment path updates only and main's skip-helper removals are intact.
  • Codex review: root entry points are now listed per engine in the README (partiql exports only Split, elasticsearch exports ParseElasticsearchREST), and make test also runs harness/conformance. The spanner harness fails without an emulator, so it has its own make test-spanner target rather than being folded into make test.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ab632d4268

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md Outdated
CI also runs harness/googlesql-spanner against an emulator, which
make test skips on purpose.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@rebelice

Copy link
Copy Markdown
Collaborator Author

Addressed the follow-up on README.md:115: make test is no longer described as the CI suite. The README now lists make test-spanner next to it and says CI runs both.

@rebelice
rebelice merged commit f240970 into main Sep 14, 2026
1 check passed
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.

1 participant