docs(blueprint): correct four statements made stale by later rules

[justinmerrell]

Refs #166.

What changes

Four prose corrections in blueprint v1. None changes what validates.

• §10 Security said a component reading viewer identity properties cannot deploy without viewerIdentity: HEADER. That predates ASSERTION and OIDC (feat(core): identity modes, machine access, installer facts and hashes #145). BP-NODE-007 requires the mode the property belongs to, and the text now says that.
• §5.2, the never-submitted paragraph returns to directly after BP-PARAM-009. BP-PARAM-004 and BP-CONNECTION-003 cite BP-PARAM-009 for it, and the corpus pins the variable not-submittable case there. feat(core): identity modes, machine access, installer facts and hashes #145 inserted BP-PARAM-011 between the two, so the paragraph read as part of the deployment-fact rule. The text itself is unchanged.
• §7, ERR_INVALID_RESOLUTION_CONTEXT. The row said only "lacks a required identity or version". BP-ACCESS-001, BP-PARAM-011 and BP-CONNECTION-002 also raise it for malformed context.
• BP-CONNECTION-002. Its diagnostic codes are set in code type, as everywhere else.

Why

#166 (S1) needs blueprint 1.7.2 cut through the post-ADR 0037 release.yml, so that its archive carries the conventions release.json and specification.json, and the release carries SHA256SUMS. blueprint 1.7.1 predates #164, and nothing has changed in blueprint since. This docs commit is a genuine correction that also triggers the patch.

Merge order: last, after component 1.6.1 is published, so that its release entry records component 1.6.1 and core 1.1.1. Rebase onto main before merging.

Compatibility

• Correction: does not change what validates.

Checks

task check passes locally: conformance, compat replay (2335 documents from 15 releases), docs, links, spelling and conventions.

🤖 Generated with Claude Code