browser-cookie-store

# Browser cookie store ## Contract | Field | Bound contract | |---|---| | Trigger | The user runs /browser-cookie-store to populate the session cookie store from installed browsers. | | Authority | Human-only local extraction. Every browser-cookie read and store write happens on the local machine. No credential is transmitted off the host. | | Side effect | The session cookie store, populated from locally installed browser profiles. No remote, paid, published, or deployed mutation. | | Done | The destination store holds extracted session cookies conforming to its schema and authenticated browsing is ready. | ## Inputs - Installed browsers on the local machine. The user may specify which browsers are present, but at least one must be available. - The destination cookie store path (supplied by the harness) and its schema (JSON, SQLite, Netscape, or whatever the harness documents). - Optional: specific browser profiles to include or exclude. ## Procedure 1. Discover installed browser profiles. Enumerate browsers present on the local machine and locate each one's profile directory. Chromium-based browsers store profiles under `<user-data-dir>/Default`, `<user-data-dir>/Profile 1`, and so on; Firefox stores them under `~/.mozilla/firefox/*.default*`. Stop if no browser is installed. Done when: the browser and profile list is confirmed non-empty or the stop is reported. 2. Read and decrypt each browser's local cookie database. Chromium stores cookies in a SQLite file (`Cookie...