Add browser match controls

docs/browser-extension.md

@@ -103,6 +103,9 @@ User story:
   access.
 - Browser matching must treat common KeePass data conventions as real browser
   targets, not just the primary `URL` field.
+- Users need explicit control over how aggressive browser matching should be so
+  they can prefer narrow page suggestions or broader candidate lists without
+  reconfiguring KeePassGO itself.
 
 Expected behavior:
 
@@ -114,6 +117,20 @@ Expected behavior:
   - scheme-less host values such as `gitlab.com`
   - custom URL fields such as `URL1`, `URL2`, and similar KeePass-style URL
     slots
+- The extension settings page exposes browser match controls for:
+  - `Best match only`
+  - `Require current scheme`
+  - `Sort results`
+- `Best match only` limits page suggestions to the strongest quality band
+  returned by KeePassGO instead of showing every candidate for the host.
+- `Require current scheme` hides `http` credentials on `https` pages and
+  vice versa when an entry stores an explicit scheme, while still allowing
+  scheme-less host entries to match either page.
+- `Sort results` affects both page suggestions and popup search results so the
+  user can prefer:
+  - KeePassGO match quality first
+  - title order
+  - path order
 
 ## Locked Vault Workflow