Add Databases to Open Session verification map - #383
Conversation
Correct drifted accessibility roles and add the recently shipped Databases surface to the feature map with a source-backed, live-proven recipe. Co-authored-by: open-session-os-tella-dev[bot] <309495949+open-session-os-tella-dev[bot]@users.noreply.github.com>
PR #359 already carries broader live-proven corrections for sessions and archived workflows. Keep this change focused on the newly shipped Databases map. Co-authored-by: open-session-os-tella-dev[bot] <309495949+open-session-os-tella-dev[bot]@users.noreply.github.com>
🤖 OS review · request changes · quality 3/5 · risk lowSafe once the verification recipe covers every mapped database behavior. 🟢 Risk low · recovery in minutes 1 inline comment below. Reviewed 🔁 Not merge-ready and no live session owns this branch — add the |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![open-session-os-tella-dev[bot]](https://avatars.githubusercontent.com/u/65127121?s=60&v=4){kind=small}
| - **Open the list.** Run `verify-opensession browser "$RUN_ID" open --route /databases --width 1440 --height 900`, take a snapshot, and require `Databases` or the `No databases yet` empty state. | ||
| - **Create a database.** Choose `New database` and wait for `dialog` named `New database`. Fill textbox `Name` with `$DATABASE_NAME` and textbox `Description` with `Created by the isolated verification pass.`. Capture the filled form, then choose `Create`. | ||
| - **Confirm stored state.** Run `verify-opensession api "$RUN_ID" /api/databases | jq --arg name "$DATABASE_NAME" '.databases[] | select(.name == $name)'`. Require one object with the entered description. Set `DATABASE_ID` from that object's `id`, then open `/databases/$DATABASE_ID`. The detail view names the saved database and shows `No tables yet`. | ||
| - **Browse or query populated data.** When a database has tables, choose one from `Table`, inspect its row count and columns, then choose `Query`. Enter a read-only `SELECT` in textbox `SQL query`, run it, and capture the result. Do not use browser evaluation or a write query to manufacture proof. |
There was a problem hiding this comment.
🟠 P2 — The recipe cannot exercise several features it claims to cover
The isolated demo has no seeded database, and the documented creation flow produces an empty database. Therefore a verifier following this conditional step skips table browsing and querying, while database-export and database-manage have no driving steps at all. A routine verification pass can consequently report this map complete without exercising queries, either download action, rename, or delete. Make querying unconditional with a table-free statement such as SELECT 1 AS result; add explicit action/result steps for whole-file download, rename, and delete; and either document an isolated way to populate a table before table browsing/CSV export or mark those paths as unproved.
Summary
Verification
bun run checkverify-20260912-060122-1991944at 1440x900 and 390x844/api/databasesNotes
PR #359 already covers the session and archive recipe drift found again in this pass, so this PR does not duplicate those edits.
Started by Daily verification skill maintenance in this OS session