You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: IMPLEMENTATION_PLAN.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -400,3 +400,27 @@ This plan lists prioritized tasks required to bring the implementation into full
400
400
- Updated `gh-attach` entry point script to use correct platform/arch detection for new binary names.
401
401
- Added unit test for MCP login tool `elicitInput` throw path (previously uncovered line 648 in src/mcp/index.ts) — verifies graceful fallback to static guidance.
constevalPrompt=`You are an automated fitness evaluator for a TypeScript project.
382
432
Your job is to score the implementation against the OpenSpec specifications below.
383
433
@@ -389,10 +439,16 @@ Your job is to score the implementation against the OpenSpec specifications belo
389
439
- "score": integer 0-100
390
440
- "reasoning": 1-3 sentences of EVIDENCE referencing the build/test/lint output, source evidence below, or specific behaviour observed. When score < 80, state explicitly what is missing or broken.
391
441
3. Do NOT bundle multiple requirements into one entry.
392
-
4. When scoring, REWARD dependency freshness:
393
-
- If npm audit shows 0 vulnerabilities, add +5 bonus points to code quality
394
-
- If npm audit shows vulnerabilities, deduct points proportionally from code quality
395
-
- If dependencies are well-maintained and up-to-date, add this as a positive observation
442
+
4. When scoring, apply these rules:
443
+
- REWARD dependency freshness:
444
+
- If npm audit shows 0 vulnerabilities, add +5 bonus points to code quality
445
+
- If npm audit shows vulnerabilities, deduct points proportionally from code quality
446
+
- If dependencies are well-maintained and up-to-date, add this as a positive observation
447
+
- CI failure penalty: if build or tests FAILED, clamp buildHealth to ≤ 30/100
448
+
- Lint warning penalty: for each 5 unique warning types, deduct 10 points from codeQuality
449
+
- Use the Source Evidence section (workflow files, package.json, test files) as AUTHORITATIVE ground truth about what is implemented. If a file is shown in the evidence, treat it as existing and implemented.
450
+
- For CI Pipeline, Release Artifacts, Semantic Release, and E2E Tests: base your scoring DIRECTLY on the workflow files and package.json shown in the Source Evidence. Do NOT assume files are absent if they are shown in the evidence.
451
+
- For E2E Tests: check test/e2e/upload.test.ts in the evidence for E2E_TESTS gating, real GitHub API calls (Octokit), and afterAll cleanup.
396
452
5. After the checklist, compute dimension averages:
397
453
- specCompliance: average of all spec-related checklist items
398
454
- testCoverage: average of all testing-related checklist items
0 commit comments