docs: close FT-113 lifecycle

[dapi]

What changed

• record the required delivery_status: in_progress transition in its own revision;
• record FT-113 closure as delivery_status: done with the implementation plan archived;
• replace pending evidence with immutable Plan Ready reviews, delivered-diff review, merge commit, and successful CI carriers.

Why

PR #114 delivered issue #113 and was merged successfully, but Feature Flow requires an explicit Execution state before Done. These two commits preserve that lifecycle sequence and close the documentation package without rewriting history.

Validation

• ruby tools/validate-priming-manifests-test.rb
• 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 lint --scope-root memory-bank --entrypoint memory-bank/README.md
• memory-bank-cli doctor --profile template
• git diff --check

Follow-up to #114 and #113.

[dapi]

Independent final closure re-review

• Reviewed head: 5c3aeee2073090e6da2c23e845c80ee36005b9e3
• Verdict: pass
• Critical findings: 0
• Important findings: 0
• CI: validate-template passed

The prior EVID-01 provenance finding is resolved: the three Plan Ready reviews remain recorded as 0/0, while delivered-diff review 5286839502 is accurately recorded as 0 critical / 1 important and linked to the distinct in_progress correction revision 41f85dffce49f46f00fc094c8df8b7504ace1801. The closure revision records delivery_status: done and archives the implementation plan.

PR #119 is safe to merge.