docs: sync Wave 1 plan with Task 0 review fixes (GetInstanceDocumentAsync, CreateApiKeyAsync)

docs/plans/2026-06-06-playwright-coverage-fill-wave1.md

@@ -354,7 +354,7 @@ public sealed class InstanceConfigureTests : IClassFixture<InstanceConfigureFixt
         await Assertions.Expect(page.Locator(".toast")).ToHaveCountAsync(1, new() { Timeout = 15_000 });
 
         // Verify persistence via CLI read-back (not just the toast).
-        using var doc = await CliRunner.GetInstanceAsync(_cfg.InstanceId);
+        using var doc = await CliRunner.GetInstanceDocumentAsync(_cfg.InstanceId);
         var bindings = doc.RootElement.GetProperty("connectionBindings");
         var bound = bindings.EnumerateArray().Any(b =>
             b.GetProperty("attributeName").GetString() == _cfg.AttributeName
@@ -530,7 +530,7 @@ public async Task CreateApiKey_RevealsOneTimeToken()
 
 **Depends on:** Task 6.
 
-**Context:** Pre-create the key via CLI (`security api-key create --name <zz> --methods <fixture method name>`) so the list has a row to act on, then drive the list-page actions. Add a `CreateApiKeyAsync` provision helper in Task 0's file if needed (returns keyId+name); otherwise create inline with `RunAsync` and resolve the keyId via `ResolveApiKeyIdByNameAsync`.
+**Context:** Pre-create the key via `CliRunner.CreateApiKeyAsync(name, methods)` (added in Task 0's review fix — it runs `security api-key create` via `RunAsync` because that command prints prose, not JSON, and resolves the new `keyId` by name) so the list has a row to act on, then drive the list-page actions. Pass `methods = _api.MethodName`. Teardown via `CliRunner.DeleteApiKeyAsync(keyId)` in `finally`.
 
 **Tests:**