feat(rules-nlp): add no-future-promises rule

[Peyton-Spencer]

Summary

• Adds the no-future-promises NLP rule for future-tense promise phrases like will help you, will enable, and will transform.
• Wires the rule into the NLP registry, public exports, README tables, and focused rule tests.
• Keeps the phrase list configurable through the phrases option for teams that want different promise patterns.

Closes #15.

Validation

• bunx pnpm@9.15.9 --workspace-concurrency=1 build
• bunx pnpm@9.15.9 --filter @faircopy/rules-nlp test
• bunx pnpm@9.15.9 --workspace-concurrency=1 test
• bunx pnpm@9.15.9 --workspace-concurrency=1 typecheck

[Peyton-Spencer]

Non-author review on head 249a667d12ad2027522221f69d4e84ade3000966.

No blocking findings. The rule mirrors the existing phrase-list pattern cleanly: configurable defaults, escaped whitespace-tolerant matching, sorted diagnostics, registry/export wiring, README coverage, and focused tests for defaults, custom override, mid-sentence matching, and registry exposure.

Verified locally with:

• bunx pnpm@9.15.9 --filter @faircopy/rules-nlp test

[Peyton-Spencer]

Non-author review on updated head 34e401ea94609e414aceb327c6ef14d668689652.

No blocking findings. I also resolved the additive conflict from PR #21 landing first by merging current origin/main into this branch and keeping both no-jargon and no-future-promises wiring/tests.

Verified after the merge update:

• bunx pnpm@9.15.9 --filter @faircopy/rules-nlp test
• GitHub CI: pass
• Merge state: CLEAN

[github-actions]

🎉 This PR is included in version 1.13.0 🎉

The release is available on:

• v1.13.0
• GitHub release

Your semantic-release bot 📦🚀