Adopt nomad-sim-parser mapping-report format for parser FEATURES.yml

[ndaelman-hu]

Purpose

The parser capability files (FEATURES.yml) were free-form, LLM-authored prose,
guarded only by a source: convention that nothing enforced. This PR reshapes them
into per-parser MAPPING_REPORT.md files that mirror the programmatic mapping
report of the new-schema simulation parsers (nomad-parser-plugins-simulation,
nomad-sim-parser mapping-report), giving a concrete, source-traceable view of which
declarative file-parser quantities reach the normalized runschema — and where coverage
is missing.

Scope

Included

• Rewrite .github/copilot-instructions.md: Markdown mapping-report format (one section
  per file-parser class: File-parser quantity | Status | Archive mapper source + a
  coverage %), a deterministic generation recipe, a grep-based self-check replacing the
  old source: field, and explicit handling of dynamically-named quantities.
• Convert all 42 in-repo parsers FEATURES.yml → MAPPING_REPORT.md, regenerated from
  parser source.
• Add docs/reference/parser_mapping_report.md, the concatenation of the fragments.

Out of scope

• molpro — it is a git submodule (nomad-parser-molpro-plugin); its report must be
  converted in that repo.
• No build tooling / CI check: the reports and combined file are maintained by hand
  (review-based trust), matching the existing LLM-authored workflow.

Context & Links

• Format modelled on FAIRmat-NFDI/nomad-parser-plugins-simulation PR Update hdf5 references #214 (parser
  coverage report) by @ladinesa.
• Supersedes the prose FEATURES.yml convention introduced in Add parser coverage AI #321/Add FEATURES.yml documentation for Wannier90, Gaussian, ORCA, ABINIT, and Wien2k parsers #323/Update all FEATURES.yml files with source field compliance #324.

Reviewer Notes

• Overall coverage across the 42 parsers is 1238/2728 quantities (45.4%). Low numbers
  (yambo, wien2k, orca, abacus) reflect heavy x_<code>_*-only extraction, not missing
  work. Eight parsers with custom archive-writing and no declarative Quantity list are
  marked "Coverage: Not available" rather than given a fabricated number.
• Coverage figures are LLM-inferred from reading each parser (each fragment self-checked
  against source), not machine-computed — please sanity-check spot cases. Regeneration
  found several latent parser bugs (e.g. elk energy_chage typo, mopac n_filled name
  mismatch, psi4 corrupted quantity name); these are documented as Unmapped, not fixed
  here.

Status

• Draft / In progress
• Ready for review
• Blocked (explain):

Breaking Changes

• None (documentation-only; no parser code changed)

Dependencies / Blockers

• None

Testing / Validation

• Manual testing (explain): each fragment self-checked — every listed quantity traces
  to a real Quantity declaration and per-section summary counts/coverage match the
  tables; combined report regenerated by concatenation.

[ladinesa]

I do not mind really having this, but considering that we will not anymore further develop the parsers here, I do not see much value. But can be merged, I guess.

[ndaelman-hu]

I do not mind really having this, but considering that we will not anymore further develop the parsers here, I do not see much value. But can be merged, I guess.

The value proposition is simple: this will help us, and in particular Cecilia and Ksenia, more easily compare parser coverage between old and new.

[coveralls]

Coverage Report for CI Build 34338698084

Coverage remained the same at 92.855%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	39079
Covered Lines:	36287
Line Coverage:	92.86%
Coverage Strength:	0.93 hits per line

---

💛 - Coveralls