[davidnmbond]

Fixes #7.

isInvestigation matched its words (investigate, research, assess, ...) against the title and the description, so a single 'assess' in a business case moved an Improvement into the investigation tiers. The words now match the title only; the investigation/research/spike labels still count. The optional heading signal from the proposal is not added: the title and label signals cover every recorded case.

Parity: no Yoda fixture changes (the full suite, including BuiltInRubricParityTests, passes), so the open question about accepting parity changes does not arise.

InvestigationClassificationTests: the issue's example (an Improvement with 'assess' only in its business case) is not an investigation, and fails without the change; each label and an 'Investigate why ...' title still are.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 4 complexity · 0 duplication

Metric	Results
Complexity	4
Duplication	0

View in Codacy

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation (-1.00%)
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (3c13989)	2071	2068	99.86%
Head commit (3547247)	2071 (+0)	2068 (+0)	99.86% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#18)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}