docs: mark lifecycle harness as historical lineage

[ndrorchestration]

Purpose

Preserve the one useful documentation-only delta from superseded registry PR #695 without reviving its stale implementation lineage.

Exact lineage

• base protected main: 972f71cf52ee7a1a7dc636eb00ed8c268496af57
• exact head: 5dcfed8ca8f17793121d63c0f5352a0a5a5f9169
• effective diff: one file, +3/-1

Change

• mark docs/lifecycle_harness_v2.md explicitly as an S067-era historical protocol/session artifact whose persona names, registry references, stability labels, and closure language do not establish current authority or control state;
• label the stability-index fence as text for Markdown hygiene.

Provenance

The wording is salvaged exactly from #695's unique docs/lifecycle_harness_v2.md patch. All registry/audit implementation work from #695 is excluded because #737 has already superseded and merged that lane on protected main.

Non-effects

Documentation hygiene only. No runtime, registry, governance, experiment, authorization, efficacy, High-Assurance, or scientific-N state changes.

Do not merge until the exact head completes the returned CI surface successfully.

[vercel]

Deployment failed for project dynamicgovernanceagenticformation with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ndrorchestration?upgradeToPro=build-rate-limit