docs: authorize LSP LaTeX implementation, precisely

Recorded as "implementation authorized" rather than "approved", because
that is what happened: the user authorized dispatch after a summary of
revision 2 four corrections, not after returning findings on the
document the way they did for the other four lanes.

The distinction matters for one reason. Section 3 .texlabroot caveat is
unverified and blocking --- texlab 5.25.1 is installed and its version
and CLI were checked, but the CLI exposes only run and inverse-search,
so its LSP-level behaviour was never established. A framing marked
plainly "approved" invites a reader to treat that caveat as settled
prose. It is step zero of the work.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai
This commit is contained in:
Levi Neuwirth 2026-08-09 17:28:52 +02:00
parent 7992054153
commit 75f5f97582
No known key found for this signature in database
2 changed files with 12 additions and 4 deletions

View File

@ -275,8 +275,12 @@ from #171 and #215.
authoritative tip** — the ref, not a SHA. Recover with
`git fetch githubsucks && git checkout lsp-latex-coverage`.
- **Framing `docs/lsp-language-coverage-framing.md`, revision 2**, in
review. **Revision 1 was UNTRACKED on `main` in one checkout** and
- **Framing `docs/lsp-language-coverage-framing.md`, revision 2 —
IMPLEMENTATION AUTHORIZED 2026-08-09**, after a summary of its four
corrections rather than a findings round on the document itself.
Recorded that way deliberately: **the §3 `.texlabroot` verification
caveat is still live and binding**, and is step zero of the work, not
a footnote it can be read past. **Revision 1 was UNTRACKED on `main` in one checkout** and
therefore did not travel; committing it here is the fix.
- **Scope: one `pmacs.lsp.config.latex` entry plus its root resolver.**
`texlab` 5.25.1 is installed and unused; a `.tex` buffer highlights

View File

@ -1,7 +1,11 @@
# LSP language coverage: LaTeX (and the Haskell/OCaml question)
**Status: framing pass, revision 2. Pre-implementation. Awaiting
approval.**
**Status: revision 2, IMPLEMENTATION AUTHORIZED 2026-08-09.**
*Recorded precisely: the user authorized dispatch after a summary of
revision 2's four corrections, rather than returning findings on the
document as they did for the other lanes. The §3 verification caveat is
therefore still live and binding — it is step zero, not a footnote.*
**Revision 2 corrects three facts revision 1 got wrong or stale, and
answers the question revision 1 named as most likely to make the entry