fix(pipeline): resolve remaining lint warnings

[pertrai1]

Summary

There are 11 lint warnings remaining in @open-forge/pipeline after getting CI to green. These are all @typescript-eslint/no-non-null-assertion warnings that should be addressed with proper null checks.

Affected Files

src/lib/helper/drift.ts (5 warnings)

• Lines 77, 78, 79, 80, 81 — non-null assertions in regex match result destructuring

tests/metrics-logger.test.ts (3 warnings)

• Lines 147, 161, 181 — non-null assertions in test assertions

tests/roadmap-task-marking.test.ts (3 warnings)

• Lines 125, 165, 252 — non-null assertions in test assertions

What was done to get CI green

The following fixes were applied in the feat/import-pipeline PR:

1. tsconfig.spec.json — overrode rootDir to "." so test files are no longer outside rootDir
2. types.test.ts — added missing rolledBackTo and attemptHashes fields to DriftSentinel test object
3. schema.ts — extracted magic numbers (300_000, 600_000) to named constants
4. manager.ts — replaced non-null assertion with proper null check
5. vitest.config.ts — extracted magic numbers to named constants
6. scanner.ts — rebuilt regex dynamically to avoid no-misleading-character-class error
7. classifier.ts → classifyTask.ts — renamed file, converted to options object param
8. generator.ts → generateRoadmap.ts — renamed file
9. parallel.ts → detectParallelGroups.ts — renamed file, extracted helpers to reduce function length/complexity/nesting
10. parser.ts — extracted findTitle, extractOverview, splitPhaseBlocks helpers from parseRoadmap to reduce function length/complexity

Acceptance Criteria

• All 11 @typescript-eslint/no-non-null-assertion warnings resolved
• nx run @open-forge/pipeline:lint produces 0 warnings