refactor: rename upstream payload to memory-bank-template while retaining downstream memory-bank

[dapi]

Goal

Rename the upstream template payload directory in this repository from memory-bank/ to memory-bank-template/.

This is a source-repository distinction only: after memory-bank-cli init or update, every downstream repository must continue to receive and use memory-bank/ as its final directory name.

Rationale

The source repository should make the template payload explicit and avoid treating its own memory-bank/ tree as an already-adopted downstream installation. Downstream projects retain the established memory-bank/ navigation, lock-file, and agent-routing contract.

Scope

• Rename the upstream payload directory to memory-bank-template/; do not retain an upstream duplicate or compatibility copy at memory-bank/.
• Update template-local documentation, links, indexes, CI, fixtures, and validation commands to address memory-bank-template/.
• Update memory-bank-cli source inspection, Git tree verification, and template-profile diagnostics to read the upstream memory-bank-template/ payload.
• Preserve the downstream destination as memory-bank/ for init, update, .lock, agent instructions, CLI defaults for downstream repositories, and all installed documentation links.
• Define explicit source-versus-downstream path terminology in user documentation and CLI implementation notes.
• Update template-profile lint/doctor behavior so source CI validates memory-bank-template/ while downstream commands retain memory-bank/ defaults.

Non-goals

• Renaming the downstream Memory Bank directory.
• Changing the public CLI executable name or command contracts.
• Supporting two upstream payload paths indefinitely.
• Changing ownership, lock schema, or managed-file semantics except where path translation requires it.

Acceptance criteria

• The template repository contains memory-bank-template/ and no upstream memory-bank/ payload directory.
• A clean downstream memory-bank-cli init installs the source payload into memory-bank/.
• memory-bank-cli update continues to compare/update the downstream memory-bank/ tree safely from a pinned source checkout.
• memory-bank-cli lint and doctor work for both contexts with clearly documented path selection.
• Template CI validates the renamed source payload; downstream smoke tests validate the installed memory-bank/ result.
• No source-template documentation incorrectly tells downstream users to create or navigate memory-bank-template/.
• The migration is covered by regression tests for init, update, doctor profile detection, and navigation.

Coordination

Implementation spans this repository and dapi/memory-bank-cli. Create and link the CLI implementation issue before changing the payload path in the template repository; merge template-side rename only after the CLI release that understands the new source path is available.

[dapi]

Routing record (2026-07-23): Refactoring Flow. Small Change is ineligible because source payload discovery and CI/CLI integration paths change; this is a behavior-preserving source-structure migration whose downstream memory-bank/ contract must remain unchanged.

Validation profile: standard. The source/downstream path translation is a compatibility-sensitive file-layout and cross-repository integration boundary; init, update, lint, doctor, navigation, and CI regression evidence are required. No high-risk or release-deployment trigger is identified for the template-side change itself.

Required separate CLI handoff created: dapi/memory-bank-cli#14. Its release is the dependency gate before this repository can merge the payload rename. This issue remains responsible only for template-side work and evidence.