Pass 1 — Test Infrastructure and Verification Constraint
Following canonization of CC-TX-2026-05-28-001, Paula completed Pass 1 of the implementation queue: test infrastructure for vault persistence and draft save/load.
`Package.swift` received a `.testTarget` declaration for `ConCOREdanceTests` pointing to `Tests/ConCOREdanceTests/`. This is the project's first test target.
`VaultStore` was refactored minimally to support URL injection. A `vaultURL: URL` instance property replaced the direct use of the `Self.vaultURL` static in `save()`, `unlock()`, `vaultExists`, and `exportBackup()`. An `init(vaultURL: URL = VaultStore.defaultVaultURL)` was added; the static was renamed `defaultVaultURL`. Production behavior is unchanged — the default argument preserves the original path. Test code passes a temporary URL in each test case and cleans up on tearDown.
`VaultCryptoError` gained `Equatable` conformance so tests can assert specific error cases without pattern-matching boilerplate.
Three test files were written, totaling 38 XCTest methods:
`VaultCryptoTests.swift` covers the encryption layer directly: round-trip correctness, wrong-password rejection with specific error type, uniqueness of ciphertext across calls using the same password and plaintext, and empty-data handling.
`VaultStoreTests.swift` covers the full store lifecycle at MainActor: createVault unlocks the store and writes the vault file, short passwords are rejected, lock clears all published state, unlock with correct password restores session count, unlock with wrong password stays locked, updateSessionDraft persists across a lock/unlock cycle, draft status promotes to `.draft` when any field is filled, and the document artifact status advances to `.drafting`.
`FixtureAndDraftTests.swift` covers ClinicalFixtureData integrity (session count, modalities, pronouns, duration, chronological order, unique IDs, artifact initial status) and generatedDraftPreview behavior (empty fallback, client name presence, modality in preview, continuity signal titles, filled fields appear without fallback, whitespace-only fields still trigger fallback).
Separately, the live archive page was updated: CC-TX-2026-05-28-001 was missing from the index page, the transmission timeline, and the manifest. Its `transmission.html` and `metadata.json` were created, the index card was added at the top of the timeline, and the manifest count was updated from 12 to 13.
Cody verified the implementation files and ran `swift build` successfully. `swift test` did not run to completion because the active developer path is `/Library/Developer/CommandLineTools`; `xcrun --find xcodebuild` fails, and the SwiftPM test build cannot import XCTest. This is recorded as an environment/tooling constraint rather than a failed test assertion.
Decisions
- VaultStore URL injection is the minimum refactor needed for test isolation; production path is unchanged.
- Tests are grouped by layer: crypto, store lifecycle, fixture/draft — not by feature.
- `@MainActor` is applied to the VaultStore test class, not per-method, since all VaultStore interactions require main-actor context.
- No mocking of VaultCrypto — tests exercise the real 120,000-iteration KDF. Test suite will be slow by design; this is the intended behavior.
- Archive HTML is maintained manually; no automation was added this pass.
- Current local verification is build-only until Xcode/XCTest tooling is available.
Next Actions
- Cody: rerun `swift test` after XCTest/xcodebuild tooling is available.
- Paula Pass 2: implement `completeSession(_ id: UUID)` on VaultStore — status `.complete`, artifact `.readyForReview`; add a restrained confirmation button in `ActiveSessionHeader`.
- Paula Pass 3: inline-editable continuity signals in the right rail.
- Paula Pass 4: copy-to-clipboard and `.txt` export from `GeneratedDraftPreview`.