[QuintinBotes]

Refs #1248: the revision of 0071 asked for there, so the merge side can land after #1333.

Why

0071 decision 1 says #1248 decides the merge side with the same per-source flag, and the record had no decision for it. With governance off, a same verdict at AUTO_CONF merges whatever the source said about its names; #1248 measured what that does on a small local model.

What changes

Docs only, in 0071-a-source-may-declare-its-names-identities.md:

• Decision 7: a same verdict at or above AUTO_CONF on a pair where either side is an identity entity (a name fact with evidence from an identity source, the join decision 4 uses) is escalated with escalate_identity instead of merged, on both paths that apply a verdict (apply_verdict with governance off, the second look included, and apply in governance.rs). It reuses the execution gate's escalation (0027). kept verdicts still close; a person's merge is unchanged.
• Dead ends: the per-base auto_merge: false that Let a knowledge base turn off automatic entity merges, independent of governance #1248 first asked for, and closing same between two identity names as kept (two producers can push one thing under two names).
• Tests the code PR adds: a_same_verdict_on_an_identity_entity_waits_for_a_person.
• Status line now says seven decisions are open; the Related line points Let a knowledge base turn off automatic entity merges, independent of governance #1248 at decision 7.

How it was checked

Read against dev: apply_verdict in adjudication.rs (the escalate_impact branch this reuses) and apply in governance.rs. No code changes here.

Before review

• Every commit is signed off (git commit -s)

[WaylandYang]

This is the revision #1248 asked for; the code PR waits for #1333's identity flag. Both this and #1333 rewrite 0071's status line, so whichever lands second rebases that one line. Approving.