Move the maintenance notes out of the evaluation repo

[sqlparser]

docs/maintenance-notes.md was maintainer history — a 31 KB account of the 2026-07 cleanup, opening with its own disclaimer that "none of this is needed to use the demos".

It was linked six times from the README, including second in the top nav bar. So the earliest thing a visitor could click, before running anything, was a table reading: 28 open Dependabot advisories, 25 committed jars, 3 tests failing and documented as expected, 263 files whose path contradicted their own package line. Then the section titles — "The 3 known failures that were not", "four breakages and a merge", "Two demos that crashed instead of explaining themselves".

All of that is fixed, and the candour is what made the document good. But this repository is what people clone to decide whether to buy the parser, and a public catalogue of past defects in the nav bar works against that. The audience for the content is whoever maintains this repo next — not the audience the repo is for.

It also showed the cost of being on the ALLOW list

check-stale-docs.sh had to exempt it — its job is naming things that were deleted. Which meant the one guard we have could not see it drift, and it had:

• a test count two releases stale (144, now 156)
• five references to connector/, renamed the day before in Take the JDBC connectors off the trial path, drop /fromdb, add a schema that fits #55

ALLOW is now README.md alone, with a comment explaining why to keep it that way.

Where it went

docs/gsp_demo_java-maintenance-notes.md in the private sqlparser/gsp_java repo, with a header recording where it came from, the two facts corrected on the way over, and that its change log stops at 2026-08-12 (so it does not cover #51–#55). That copy is currently uncommitted in that checkout — committing to a second repository is your call, not something to fold into this PR. This repo’s git log keeps the full history either way.

Nothing is lost from the README

The two deep links that carried substance are inlined where they were referenced, so both warnings now stand on their own:

• the four package roots and 263 contradicting files, at the -Dexec.mainClass note
• all four pom_dlineage.xml breakages, at the "don’t add a second POM" warning

Two broken links, fixed on the way

Nothing checks relative links, and two had rotted: columnImpact pointed at ../dlineage, which from that directory resolves to antiSQLInjection/dlineage; search pointed at ./visitors from inside search/. Every relative link in all 64 tracked markdown files resolves now.

I checked that with a throwaway script rather than a committed one. Wiring a link check into build.yml alongside check-stale-docs.sh is the obvious follow-up — it found two real breakages in seconds — but that is another permanent CI step, so I left it out of this PR.

Verified

156 tests · stale-docs self-test 5/5 and clean scan over 63 files · licensed-only guard 3/3 · dlineage jar in JSON and XML · parser version consistent at 4.2.6.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UK3dBXFXqiDRYJxz1YxWCr