AI CODING TOOL EVALUATION BRIEF AND BLANK SCORECARD
ShowMeYourSaaS — October 26, 2026
Guide: https://showmeyoursaas.com/articles/best-ai-coding-tools/

This is an ORIGINAL UNFILLED EVALUATION PROTOCOL. We have not measured the four
vendors against it. No scores, costs, or rankings below are observed results.
Official capability sources and the documentation-check date are in the guide.

FAIR STARTING POINT
Test repository (permitted synthetic data only):
Starting commit, same for each candidate:
Runtime, dependencies, and setup:
Documented test/build commands:
Reproduced failing behavior before the attempt:
Expected unchanged behavior:
Time and spending ceiling:
Allowed files, commands, network access, and connected tools:
Use a disposable branch/worktree for each attempt.

ORIGINAL MAINTENANCE BRIEF
In this test repository, submitting a title containing only spaces incorrectly
creates a record.

Reproduce the behavior. Find the authoritative validation path. Reject
whitespace-only titles while preserving valid titles and the existing stored-data
format. Add a regression check for the invalid case and confirm a valid title
still saves.

Use the repository's documented commands. Keep the change focused; explain any
proposed dependency change before making it. Use synthetic data. Do not send
messages, change live services, push, merge, or deploy.

Report the cause, diff, actual command results, remaining limitations, elapsed
time, and usage or cost evidence available in the tool.

ONE SCORECARD PER TOOL AND ATTEMPT — LEAVE UNKNOWN VALUES UNKNOWN
Tool, version/surface, plan, and model if disclosed:
Date and repository commit:
Permission configuration:
Setup deviations from other attempts:
Did the tool reproduce the original failure? Evidence:
Did it identify the authoritative validation path? Evidence:
Does the new regression check fail before and pass after the change?
Does a valid title still save? Evidence:
Other existing checks actually run and their results:
Unrelated files, dependencies, or behavior changed:
Reviewer understanding of the diff:
Incorrect claims or missing verification:
Unresolved limitations:

EFFORT AND COST
Setup minutes:
Tool execution/wait minutes:
Human correction minutes:
Review and verification minutes:
Available usage/cost evidence and what it excludes:
Subscription allocation or metered charges (state method):
Final decision and reason:

Repeat on a different maintenance task before generalizing. A successful form
fix does not establish migration quality, architectural fit, or reliability on
concurrent data changes. Check current vendor billing and organization policies.