Issues

The unsupported-language fields in card.go are dead code — #27 shipped 1 of 6 slices

#52

· iksnae opened

on Jul 29, 2026

--detailed renders the card, not the detailed report — and is the fifth declared-and-never-wired artifact in this subsystem

#51

· iksnae opened

on Jul 29, 2026

VS Code extension re-derives pass rate and disagrees with the CLI (0.0% on unassessed repos); no CI covers it

bug

#49

· iksnae opened

on Jul 29, 2026

recordJSON.Version is written but never validated — mixed tool versions silently mis-certify

#48

· iksnae opened

on Jul 29, 2026

Three follow-ups from the unsupported-language review: an untested load-bearing skip, GradeNA ordinality, and a duplicated counter

#45

· iksnae opened

on Jul 28, 2026

Decide: what should --mode enforcing exit when no unit could be assessed?

#44

· iksnae opened

on Jul 28, 2026

Three predicates for 'is this language supported?' — engine and report layer can silently disagree

#43

· iksnae opened

on Jul 28, 2026

flaky-test: TestGenerateSite_LargeScale hard <10s wall-clock bound fails non-deterministically, blocks unrelated work at review gate

bug

#42

· iksnae opened

on Jul 23, 2026

Guard Score() with language-tier gate, protect complexity maintainability rule, remove 0.5 defaults, update pipeline, and fix all engine tests

agencyx:done

#31

· iksnae opened

on Jul 15, 2026

Run the full test suite (go test ./... -count=1), fix any regressions in existing tests that assumed all languages produce full dimension sets or non-N/A grades, and ensure the build compiles cleanly.

agencyx:blocked

#28

· iksnae opened

on Jul 15, 2026

Add comprehensive tests in scorer_test.go: unsupported language → N/A, unmeasured complexity not scored as excellent, Swift-like generic unit produces no fabricated dimensions, and regression tests for each fix area.

agencyx:blocked

#26

· iksnae opened

on Jul 15, 2026

Guard Score() and scoreFromMetrics in scorer.go: short-circuit unsupported languages to N/A, protect the complexity-based maintainability rule from firing on unmeasured zero values, and reconcile 0.5 dimension defaults with the Score() doc contract.

#25

· iksnae opened

on Jul 15, 2026

Navigation Menu

All issues

The unsupported-language fields in card.go are dead code — #27 shipped 1 of 6 slices

--detailed renders the card, not the detailed report — and is the fifth declared-and-never-wired artifact in this subsystem

VS Code extension re-derives pass rate and disagrees with the CLI (0.0% on unassessed repos); no CI covers it

recordJSON.Version is written but never validated — mixed tool versions silently mis-certify

Three follow-ups from the unsupported-language review: an untested load-bearing skip, GradeNA ordinality, and a duplicated counter

Decide: what should --mode enforcing exit when no unit could be assessed?

Three predicates for 'is this language supported?' — engine and report layer can silently disagree

flaky-test: TestGenerateSite_LargeScale hard <10s wall-clock bound fails non-deterministically, blocks unrelated work at review gate

Guard Score() with language-tier gate, protect complexity maintainability rule, remove 0.5 defaults, update pipeline, and fix all engine tests

Run the full test suite (go test ./... -count=1), fix any regressions in existing tests that assumed all languages produce full dimension sets or non-N/A grades, and ensure the build compiles cleanly.

Add comprehensive tests in scorer_test.go: unsupported language → N/A, unmeasured complexity not scored as excellent, Swift-like generic unit produces no fabricated dimensions, and regression tests for each fix area.

Guard Score() and scoreFromMetrics in scorer.go: short-circuit unsupported languages to N/A, protect the complexity-based maintainability rule from firing on unmeasured zero values, and reconcile 0.5 dimension defaults with the Score() doc contract.

Search results