# L2 metadata range evidence for the D2A Catalog schema closure

This evidence is bound to the L2 metadata ref change that follows downstream
PR #4214 and compares the exact `nexuscrm-pingcap-pack` revisions:

- previous: `2408dbb92759b4290b88973cf813bfec5b66455a`
- candidate: `34738b2fc97e425bc4bf84320fe086c243a5b971`

## Why the previous artifact cannot be selected

The previous final-pack lineage selects NexusCRM metadata builder
`d7dd71df63ac697d11a8df853ddd3715b8f4b8db`. After the Catalog reconciler was
advanced to `nexuscrm-controlplane@2178447f...`, the existing resolved-BOM
producer compared the Catalog command's authoritative kernel schema with that
metadata builder and failed closed:

```text
serviceification system-schema compatibility failed: metadata schema is
missing required index on _System_ConnectorRemoteLink:
{"columns":["RemoteLocatorHash"],"name":"idx_connector_remote_link_locator"}
```

The failure is recorded by resolved-BOM candidate run
[`29779353737`](https://github.com/pingcap-inc/nexuscrm-pingcap-pack/actions/runs/29779353737).
No resolved BOM was published or signed.

## Complete selected-artifact range

The Git range contains 10 commits. Nine change release orchestration, tests or
documentation without changing the selected final-pack tree. The candidate
commit `34738b2f...`, merged from `pingcap-inc/nexuscrm-pingcap-pack#4142`, is
the only commit in the range that changes `packs/NOT-EDIT-final-merged-packs`.

That reviewed pack change:

- advances the final-pack metadata-builder lineage to
  `NexusCRM@038ca5b7405d2080d07ed50324b9a3c4fc6f73c4`;
- advances the official CRM pack input to
  `nexuscrm-app-packs@1954b5fa2e8e307cd3a66e27d7c8b79eeacba59e`;
- adds the reviewed Account and Opportunity field-history policy and its
  matching frontend report-source support;
- preserves the generated final-pack/source agreement and deterministic
  regeneration contract.

The final exact head of #4142 passed both standard and adversarial review, the
release-tuple and double-build regeneration gates, final-pack metadata audit,
the field-history policy tests, clean install, upgrade and idempotent reapply.

## Exact compatibility and identity

The candidate metadata builder contains the Catalog-required
`idx_connector_remote_link_locator` index. Running the same checked-in verifier
used by the resolved-BOM producer against:

```text
Catalog kernel: nexuscrm-controlplane@2178447f... module closure
metadata schema: NexusCRM@038ca5b7.../nexuscrm-kernel/pkg/schemacatalog/system_tables.json
```

returns:

```text
serviceification system-schema compatibility verified
```

The canonical final-pack contract digest for the candidate, excluding only
`.build-lineage.json` as defined by that owner, is:

```text
sha256:0695b3e5bec0d43592ca226890335fe04cbbf3bd346ce12f3635a06ea153eaf9
```

The desired BOM binds this same commit in both `frontend.l2_commit` and
`l2_metadata.commit`; it does not combine frontend and metadata from different
L2 snapshots.

This file is review evidence only. The desired BOM remains non-deployable. A
new frontend and resolved BOM must still be built, owner-signed and verified,
and the real test2 activation must still prove query parity on the selected
metadata before D2A can advance.