AutoFillExtension

This target provides password, passkey, one-time-code, and new-credential save/generate fulfillment through AuthenticationServices.

Main Files

CredentialProviderViewController.swift is the extension entry point for interactive and silent credential requests.
AutoFillSearchView.swift renders the searchable SwiftUI UI shown inside the extension.
AutoFillEntryCreatorView.swift renders the credential-creation UI used for save-password requests and strong-password generation follow-up.

The extension looks up the active database through ../KeeForge/Services/Persistence/DatabaseListStore.swift and reads the shared cached database copy from the App Group container.
It reuses ../KeeForge/Models plus a selected subset of service files declared explicitly in ../project.yml.
Unlock can use stored composite keys plus biometrics for quick AutoFill, or fall back to interactive password entry.
Password and passkey requests both parse the database locally; the extension does not depend on the main app being open.
Save-password requests now prefill a new entry via ../KeeForge/Services/AutoFill/AutoFillSaveCoordinator.swift, save encrypted bytes through ../KeeForge/Services/Persistence/LocalDatabaseSaver.swift, and enqueue ../KeeForge/Services/Cloud/PendingUploadQueue.swift markers for cloud-backed databases before returning success.

Keep dependencies extension-safe. If the extension needs another service file, add it explicitly to the KeeForgeAutoFill sources in ../project.yml.
Changes to App Group storage, shared defaults, cached database copy semantics, or Keychain semantics usually affect both targets.
Relevant tests are usually in ../KeeForgeTests/CredentialProviderSaveTests.swift, ../KeeForgeTests/CredentialIdentityStoreManagerTests.swift, ../KeeForgeTests/CredentialMatcherTests.swift, ../KeeForgeTests/PasskeyTests.swift, and ../KeeForgeTests/SharedVaultStoreTests.swift.