bumicerts · agentic-refresh-20260513-credentials

Bumicerts credential refresh agentic test

@satyam-mishra-pce

A fresh rerun with refreshed test-account auth resolved the previous public Explore and auth-state blockers, added videos, and verified durable PDS/indexer writes; the run remains partial because the create/publish UI did not reach the expected final success state.

Date: 2026-05-13 · Target: http://127.0.0.1:3001 · partial


Headline result

4
flows/checks passed
1
partial blocker
4
videos embedded
6
indexed activities

Credential refresh improved the result. Server health was confirmed, Explore passed, upload organization save passed, and PDS/indexer both show the fresh activity record at 2026-05-13T11:03:59.306Z. The only remaining failure is the create/publish UI assertion waiting for Published! even though the durable record exists.

Video walkthroughs

Videos are embedded intentionally. Each video below was selected by explicit filename and listed in the final media manifest. The create video is labeled partial/failure evidence, not a pass.

Explore render — pass

Create/publish — partial: durable write exists, final UI state failed

Upload organization save — pass

Authenticated route sweep — pass

Reviewed screenshots

Explore page rendered
01 ExploreFresh Explore capture after server health check; the prior sign-in panel did not reproduce.
Authenticated upload dashboard
02 Upload dashboardRefreshed auth state reached the upload dashboard.
Upload edit mode
03 Edit modeOrganization edit mode was reachable.
Authenticated create hub
04 Create hubAuthenticated create hub was reachable with refreshed auth.
Create publish final UI failure
09 Publish UICreate/publish progressed to publish but failed waiting for the final Published UI state.

Data verification

PDS and indexer agree. Both verification files show 1 location and 6 activity records for the test DID, including the fresh create/publish record at 2026-05-13T11:03:59.306Z.

PDS verification: assets/pds-verification.md
Indexer verification: assets/indexer-verification.md
Create/publish log: assets/e2e-create-publish.log
Upload save log: assets/e2e-upload-save.log
Explore log: assets/e2e-explore.log

Findings

Explore public browsing now passes

The server was healthy and the fresh Explore screenshot/video show the route rendering instead of the previous sign-in error panel.

Authenticated upload organization save passes

The refreshed auth state reached the upload dashboard/edit mode, and the upload save E2E scenario passed with video evidence.

PDS/indexer verification passes

PDS and GraphQL indexer checks agree on the location and activity records. This addresses the previous inability to compare indexer state.

Create/publish remains partial at final UI state

The create flow made it through the wizard and publish click, and durable records show a fresh activity write. The UI/test still failed waiting for the expected Published! success state, so the report cannot honestly be marked pass.

Media QA and secret handling

No secret values are printed in the report. Credential material was loaded from an ignored local secret source and was not embedded in media. Every embedded visual asset is listed in assets/final-media-manifest.md; no wildcard media embedding is used.

Reproducing

Run slugagentic-refresh-20260513-credentials Targethttp://127.0.0.1:3001 Secret sourceIgnored local file used by the test runner; values are not included here. Primary checkscucumber-js feature/name runs for Explore, create/publish, and upload org edit/save. Evidence sourceagentic-tests/runs/agentic-refresh-20260513-credentials/auth/ in the Bumicerts app checkout.