[Pipeline: provenance] Enforce raw manifest and docstring traceability for VASP

[newtontech]

tracking_id: lsp-perfect-20260615-vasp-lsp-provenance

Problem

Repo maintainability depends on every runtime rule and code docstring being traceable to LLM Wiki and raw evidence.

Target Repository

• Repository: newtontech/VASP-LSP
• Software/backend: VASP
• Pipeline stage: provenance

Scope

• Require code docstrings/doc comments to link to concrete wiki/*.md pages.
• Require wiki raw references to exist and be represented in raw/assets/manifest.json.
• Generate reports/docstring-wiki-raw-traceability.json or an equivalent provenance report in CI.

Acceptance Criteria

• docstringsTotal equals docstringsLinked in the traceability report.
• brokenWikiLinks, wikiSourcesWithoutRaw, and rawManifestFailures are zero.
• The provenance report is committed and guarded by automated tests or CI scripts.

Deterministic Verification

• python3 scripts/check_docstring_traceability.py --write-report --strict
• python3 -m pytest tests/test_docstring_traceability.py when the repo is Python-based.

Implementation Notes

• Follow the repeatable pipeline: official documentation capture -> wiki schema/rules -> provenance -> tests/evals -> LSP runtime/OpenQC integration.
• Keep version-specific behavior explicit. Do not collapse incompatible software versions into one rule.
• Do not claim parity with Python/C++ LSPs until diagnostics, completion/hover/symbols/format/fix surfaces have evidence and tests.
• Link code docstrings to concrete wiki/*.md pages, and link every wiki source claim to a tracked raw/... asset when this stage touches code or docs.

[newtontech]

OpenQC traceability contract update (2026-06-15)

OpenQC PR newtontech/OpenQC-VSCode#234 merged the shared traceability report contract. This issue now has a concrete compatibility gate:

• Required schemaVersion: openqc.lsp.traceability.v1
• Preferred report path: reports/docstring-wiki-raw-traceability.json
• Required top-level fields: serverId, repository, languageId, generatedAt, summary, docstrings, wikiSources, ruleIds, sourceUrls, rawManifest
• Rule ID format: <BACKEND>-<FILE_ROLE>-<CATEGORY>-NNN
• All code/wiki/raw paths in the report must be repository-relative; hidden local absolute paths are invalid.

Current OpenQC family-gate status for newtontech/VASP-LSP: missing report

Report path observed by OpenQC: not found

Current evidence:

• No reports/docstring-wiki-raw-traceability.json or accepted traceability report path was found by OpenQC.

Additional acceptance for closing this issue:

• The repo emits reports/docstring-wiki-raw-traceability.json with schemaVersion: openqc.lsp.traceability.v1.
• summary.docstringsLinked == summary.docstringsTotal and all failure counters are zero.
• The report contains non-empty docstrings, wikiSources, ruleIds, sourceUrls, and rawManifest sections where applicable.
• CI or a deterministic test validates the report shape and repo-relative paths.
• OpenQC latest family gate no longer reports this repo under traceability schema failures or missing traceability report warnings.

Reference contract: newtontech/OpenQC-VSCode docs/lsp-traceability-report-contract.md and docs/schemas/lsp-traceability-report.schema.json at merge commit 745b1e75f25f79db374ed16ca1463620131a99ab.