# SKD Credential Manager — isolated Google review kit

This environment contains **synthetic data only**. It does not enroll a device, connect to the owner's vault, access email/SMS accounts or contain production keys. The extension under review is version 1.4.7, Store ID `iijenlmkbkolaemalkplgnjanfaenpma`.

## Setup

Use a disposable Windows user or Windows VM with Chrome, PowerShell 7, and Node.js 22.19 or newer. The helper refuses to replace an existing SKD native-messaging registration. No administrator account, production login or owner certificate is needed.

1. Extract the ZIP. In PowerShell 7, run `./review/Start-Review.ps1 -Action Start` from its root. The helper creates a seven-day, local-only synthetic TLS certificate; it does not import a trusted root into Windows or Chrome. The authority requires that same local client certificate and binds only to loopback.
2. Use the Store item under review installed by Chrome. For independent pre-submission testing, the included `extension` directory is the same packaged code with Google's verified public identity key supplied in its manifest; loading this directory unpacked produces the exact Store ID. This is an alternative to the Store installation, not a second extension to install alongside it.
3. Open `http://127.0.0.1:41487/`. The helper never submits website forms. Reviewers use the website's buttons after insertion.

## Test scenarios

- **Discovery, popup, sidebar, selection, reveal and copy:** choose Login. The popup and sidebar offer Sample Main and Sample SKD. Select either account, use Insert Credential, and verify the page shows that selected username and a populated password. Hide/show and both Copy controls work independently. Submit to proceed to verification.
- **Two-page login:** choose Two-page login. Insert the username and click Next; insert the password on the next page. Existing matching values are preserved by automatic filling.
- **Automatic login and verification:** enable the separate automatic-fill switches in the sidebar. Reload a login page. Submit it, then verify that the authenticator code appears automatically in the verification field. Click Verify; the local site must show Sign-in accepted. The TOTP values use a synthetic seed and expire every 30 seconds. Email/SMS selections use simulated fresh delivery through the same resolve/complete protocol; this kit does not demonstrate a real provider delivery.
- **Questions:** open security questions and select Which synthetic planet? The synthetic answer is Synthetic Neptune.
- **New credential:** choose New credential; username is `review.new@example.test`. Enter password `Review-New47!`, submit, and choose Add New Credential in the sidebar. Refresh and confirm it is available. Alternatively use the sidebar's manual password field.
- **Update:** for `review.main@example.test`, enter `Review-Updated47!` on Login, submit, and choose Update Existing Credential. Refresh and verify the new password. The save has a dated browser provenance tag. Matching username capitalization does not create a new account.
- **Isolation:** other origins cannot retrieve these credentials. Real account names and arbitrary passwords are rejected. The native helper accepts only the exact Store ID. No password or code is stored in Chrome recovery caches.

Initial synthetic usernames: `review.main@example.test`, `review.skd@example.test`. Initial synthetic password: `Review-Planet47!`. Use only these usernames, plus `review.new@example.test`; passwords must begin `Review-` followed by letters, digits or `!`. These are public test values, not production credentials.

## Recovery and removal

The authority holds at most three synthetic accounts and 128 operation outcomes in memory. Native-helper reconnects retain the authority's current synthetic state; stopping/restarting the authority resets it. This regenerable review fixture is not a durable credential store and must never be used for real accounts. Production uses the owner's authenticated PostgreSQL authority.

To stop and unregister, run the kit's `./review/Start-Review.ps1 -Action Remove`. The files remain for inspection. To start a fresh fixture, choose a new root, for example `-Root "$env:LOCALAPPDATA/SKD/ReviewSecondRun"`; unregister the previous one first. Optional `-PagePort` and `-ApiPort` change both loopback ports.

The kit verifies native protocol, synthetic service behavior and package code. Pre-submission automated tests are not a claim that Chrome's final Store installation or production email/SMS delivery was observed. Google reviewers can validate the installed item through the workflow above without owner access.