refactor(domain): enrich NoteInput with extractScopeAndTags (#210)

[pajoma]

Summary

• Moves SCOPE_DEFAULT from src/vscode/conf.ts → src/model/config.ts (re-exported for backward compat)
• Changes Input._text/_scope/_tags from private → protected; _scope initializes to SCOPE_DEFAULT at field declaration (no more empty-string default)
• Adds NoteInput.extractScopeAndTags(availableScopes: string[]): void with hardened regex /#\w+(?:\s|$)/g (handles end-of-string tags)
• Parser.resolveNotePathForInput delegates to extractScopeAndTags; removes inline tag loop and now-unused imports
• LoadNotes constructor narrowed to NoteInput; callers updated with type assertions
• 5 unit tests added (no vscode API needed; pure sync)

Closes #210

Spec: docs/specs/2026-05-17-210-rich-domain-models.md
Plan: docs/plans/2026-05-17-210-rich-domain-models.md

Test plan

• npm run compile — clean build
• npx tsc --noEmit — no type errors
• Run extension tests: NoteInput.extractScopeAndTags suite (5 scenarios including end-of-string regex coverage)
• Manual smoke test: open note with #scope tag, verify scope routing and tag stripping

🤖 Generated with Claude Code

[pajoma]

Architecture Review: Final Approval (PR #216)

I have performed a critical architectural and OOP-focused review of this PR. The implementation is technically sound and represents a significant maturity leap for our domain layer.

Key Achievements:

• OOP Maturity: Successfully transitioned to a Rich Domain Model by moving internal state normalization (extractScopeAndTags) into the model. The use of protected fields correctly balances encapsulation with subclass extensibility.
• Structural Integrity: Migrating SCOPE_DEFAULT to model/config.ts ensures our business invariants are decoupled from the platform integration layer.
• Regex Robustness: The hardened regex (/#\w+(?:\s|$)/g) resolves a long-standing edge case for end-of-string tags, improving the reliability of the "Smart Input" feature.
• Improved Testability: The addition of pure, dependency-free unit tests for the model demonstrates the immediate value of this refactoring for our CI feedback loop.

Final Observation:

While the type assertions (as NoteInput) in the UI and Action layers are a temporary byproduct of our transition, they are acceptable pragmatic tradeoffs that allow us to enforce correct subclassing in our core features (LoadNotes).

This is a high-quality, domain-driven refactor. LGTM.

---

Note: Gemini was involved in creating this comment (but not without consulting me).