Repository navigation
Commit 0aaec39
committed
feat(uts-to-kotlin): deterministic selection via resolver script + evaluate mode
Make the skill's selection phase deterministic and add an explicit
translate-vs-evaluate choice:
- Add scripts/resolve_uts.py — a bundled resolver that validates the module
directory, reads uts-package-mapping.json, and emits JSON with, per tier,
the target dir, Kotlin package, and the candidate specs with derived class
names. This replaces the per-run hand-work (regex validation, path joins,
snake_case->PascalCase) that the model previously improvised, so Phase 1 is
byte-for-byte deterministic. Exclusions are checked relative to the tier
base (robust to the checkout location), and --create guards the target name.
- Rewrite Phase 1 (Steps A-E) around the resolver: resolve, confirm/create
mapping, choose tier, choose specs, choose translate-only vs evaluate.
- Gate Step 6 (run/fix) behind evaluate mode per writing-derived-tests.md's
Translation (always) vs Evaluation (only when an implementation exists)
split; translate-only stops after compile + review.
- Make the reference fetch mandatory (WebFetch added to allowed-tools).
- Fix the file template to use the resolver's package/className (no hardcoded
realtime, no double Test suffix) and the spec's full @uts id; correct stale
uts/test/... proxy doc paths.1 parent 940b65f commit 0aaec39
2 files changed
Lines changed: 270 additions & 128 deletions
0 commit comments