docs(cli): clarify test and submit command behavior for uncommitted changes

AGENTS.md

@@ -68,9 +68,10 @@ bun run stats           # terminal dashboard over GET /api/stats — four panes
                         # r refetches, q quits. Outside a TTY it prints every pane once.
                         # SRS_API points it at a local Worker like close-solved does.
 bun run test            # run ONE solution against LeetCode's judge (not a test suite;
-                        # most recently tested first, stamped in the db on exit 0)
+                        # files git sees as modified/untracked first, so Enter runs the
-bun run submit          # submit ONE solution to LeetCode (newest scaffold first, nothing
+                        # one in progress; then most recently tested; stamped on exit 0)
-                        # hidden; last_submitted stamped in the db on exit 0)
+bun run submit          # submit ONE solution to LeetCode (uncommitted first, then newest
+                        # scaffold, nothing hidden; last_submitted stamped on exit 0)
 bun run sync            # work/1 → apps/docs/content/ pages + apps/docs/redirects.ts (/<num> short
                         # links; re-solves are never published)
 bun run videos          # docs pages with no `video:` frontmatter → NeetCode video per page