Record dataset catalog live verification
This commit is contained in:
@@ -2592,9 +2592,11 @@ Tested:
|
|||||||
- Local browser check against `http://127.0.0.1:5175` with live API proxy: Data workspace showed Selected, Reference, Candidate and Source summary cards, with 1 Reference, 1 Candidate and 0 Source in the demo catalog; dataset badges rendered correctly on desktop and mobile, no console warnings/errors and no horizontal overflow.
|
- Local browser check against `http://127.0.0.1:5175` with live API proxy: Data workspace showed Selected, Reference, Candidate and Source summary cards, with 1 Reference, 1 Candidate and 0 Source in the demo catalog; dataset badges rendered correctly on desktop and mobile, no console warnings/errors and no horizontal overflow.
|
||||||
- Screenshots captured under `artifacts/sprint68-dataset-catalog-density/`.
|
- Screenshots captured under `artifacts/sprint68-dataset-catalog-density/`.
|
||||||
- `bash scripts/run_readiness_check.sh` (`243 passed`)
|
- `bash scripts/run_readiness_check.sh` (`243 passed`)
|
||||||
|
- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/deploy_tower.ps1` rebuilt and redeployed the Tower all-in-one container, with live migration smoke and browser runtime verification passing.
|
||||||
|
- Live post-deploy Data catalog check on `http://192.168.10.150:1202`: Data workspace showed Selected, Reference, Candidate and Source summary cards, candidate/reference badges rendered, no console warnings/errors and no horizontal overflow on desktop or mobile.
|
||||||
|
|
||||||
Open:
|
Open:
|
||||||
- Run full readiness, redeploy Tower and verify the live Data catalog after deployment.
|
- None for this pass.
|
||||||
|
|
||||||
Limitations:
|
Limitations:
|
||||||
- This is a frontend density/readability pass only. It does not change dataset persistence, backend role validation, API contracts, migrations, provider fetching or AI/model behavior.
|
- This is a frontend density/readability pass only. It does not change dataset persistence, backend role validation, API contracts, migrations, provider fetching or AI/model behavior.
|
||||||
|
|||||||
Reference in New Issue
Block a user