P13: Add follow-up backlog from implementation gap audit

[SoundBlaster]

Description

Add the Phase 13 review outcomes into tracked FLOW artifacts:

• Added 5 actionable follow-up tasks to SPECS/Workplan.md (FU-P13-T10 .. FU-P13-T14).
• Updated SPECS/INPROGRESS/next.md to reflect the new pending backlog and next suggested tasks.
• Archived the review report to SPECS/ARCHIVE/_Historical/REVIEW_Phase13_Implementation_Gap_Audit.md.
• Updated SPECS/ARCHIVE/INDEX.md (historical index + archive log + last updated marker).

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactoring
• CI/CD improvement

Quality Gates

Before submitting, ensure all quality gates pass:

make check

Or run individually:

• make test - All tests pass with ≥90% coverage
• make lint - No linting errors
• make format - Code is properly formatted
• make typecheck - Type checking passes
• make doccheck - Documentation is synced with DocC (if docs changed)

Notes:

• This PR changes planning/archive artifacts only (SPECS/*) and does not modify runtime code.
• Full quality gates were not re-run for this metadata-only update.

Documentation Sync

If you modified files in docs/, ensure corresponding DocC files are also updated:

docs/ file	DocC file
docs/installation.md	mcpbridge-wrapper.docc/Installation.md
docs/cursor-setup.md	mcpbridge-wrapper.docc/CursorSetup.md
docs/claude-setup.md	mcpbridge-wrapper.docc/ClaudeCodeSetup.md
docs/codex-setup.md	mcpbridge-wrapper.docc/CodexCLISetup.md
docs/troubleshooting.md	mcpbridge-wrapper.docc/Troubleshooting.md
docs/architecture.md	mcpbridge-wrapper.docc/Architecture.md
docs/environment-variables.md	mcpbridge-wrapper.docc/EnvironmentVariables.md
README.md	mcpbridge-wrapper.docc/mcpbridge-wrapper.md

• Documentation changes are synced with DocC catalog (or N/A)

Testing

• Added/updated tests for new functionality
• All tests pass locally
• Manually tested the changes

Manual validation performed:

• Verified new FU-P13-T10..FU-P13-T14 tasks are present in SPECS/Workplan.md.
• Verified next.md now suggests these new follow-up tasks.
• Verified archived review file exists and is indexed in SPECS/ARCHIVE/INDEX.md.

Checklist

• Code follows the project's style guidelines
• Self-review completed
• Comments added for complex code
• Documentation updated (if needed)
• No new warnings generated
• PR title is descriptive