docs: add 4+1 viewpoint coverage

[dapi]

What changed

• Added mandatory 4+1 viewpoint coverage for designed features: Logical, Process, Development, Physical, and driving Scenarios.
• Added a Cross-View Correspondence table that traces each SC-* through requirements, runtime semantics, code/component ownership, deployment topology, and verification evidence.
• Defined explicit applicability predicates for Process, Development, and Physical views so every N/A requires evidence.
• Extended the Solution Ready gate, required minimum, and traceability contract to enforce the new coverage.
• Added a migration boundary: existing Solution Ready designs are grandfathered until their canonical solution facts materially change.
• Registered the analysis in the feature artifact catalog and linked the 4+1 concept from the root README.
• Separated external methodology sources from downstream repositories (zelma, merchantly, and mercury) that act as practical Memory Bank proving grounds.

Why

The existing architecture coverage checks components, connectors, configuration, behavior, and quality concerns, but it did not explicitly verify that one design is sufficient for different stakeholder perspectives. The 4+1 layer adds that review lens without creating duplicate canonical owners or mandatory view documents.

Impact

Every required design.md now:

• marks Logical View and Scenarios as covered;
• marks Process, Development, and Physical views as covered or justified N/A;
• links supporting projections to canonical facts instead of defining new facts;
• maps every acceptance scenario to all applicable views and CHK-* / EVID-*.

No new standalone artifact is required.

Validation

• ruby tools/validate-priming-manifests.rb template/memory-bank
• memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md
• memory-bank-cli doctor --profile template
• git diff --check