4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusen	d65f0b2091	feat(extension): probe shows current state before click; v1.0.6 ... Operator-asked 2026-05-31 (during sidecar synthetic anchor cleanup): "the add source/subscription button idea to the firefox extension so it can tell me if a source/artist is added or not and offer an option to add it if it isn't." Plan tracked in Scribe task #507. ## Backend - `ExtensionService.probe(url)` — read-only resolution. Reuses `_derive` for platform+slug, then 2 SELECTs. Returns one of: - `source_match` (exact (artist, platform, url) Source exists) - `artist_match` (artist exists, this URL isn't a Source yet; collapses the sidecar-synthetic-only case from v26.06.01.0) - `new` (neither exists) - `unknown_platform` (URL didn't match any artist-page regex) - `GET /api/extension/probe?url=...` route with `X-Extension-Key` auth posture matching `/quick-add-source`. Read-only, side-effect free. - 6 backend tests in tests/test_api_extension.py covering each state + auth + invalid URL. ## Extension - `api.js`: `probeSource(url)` mirroring `quickAddSource` shape. - `background.js`: `PROBE_SOURCE` + `OPEN_ARTIST_PAGE` handlers. The latter strips the `/api` suffix from configured `apiUrl` (placeholder format per options.html) and opens `${base}/artist/{slug}` in a new tab via `browser.tabs.create`. - `content-script.js`: probe-first render — on page-load and SPA navigation, asks the backend for the URL's state and renders the chip in the matching color/copy on FIRST paint instead of flashing generic "Add" and updating after. Click handler branches: `source_match` → OPEN_ARTIST_PAGE; `artist_match`/`new` → existing ADD_AS_SOURCE flow (then re-probes so the chip flips green immediately, no wait for next nav). - `content-script.css`: three state-color modifiers (--new, --artist-match, --source-match) on the FC parchment-on-slate palette. Sage for already-added, amber for artist-exists, accent orange for new. ## Versioning - `extension/manifest.json` + `extension/package.json` → 1.0.6. build.yml's sign-extension job will fire on push to main since no `ext-1.0.6` Forgejo/Gitea release exists yet — exercises the regenerated AMO keys end-to-end. ## Behavior on the sidecar-synthetic case Filesystem-imported "Dymkens"-style artist with only a sidecar synthetic Source: probe returns `artist_match` (not `new`), so the chip reads "+ Add Patreon source to Dymkens" rather than offering to recreate the artist. Clicking adds the real Source; existing `_source_for_sidecar` preference logic (v26.06.01.0) routes future gallery-dl Posts to the real one.	2026-06-01 00:41:17 -04:00
bvandeusen	2394e47370	fix(hentaifoundry): inject host-only PHPSESSID/CSRF duplicates + extension preserves browser hostOnly ... Operator-flagged 2026-05-27: HF source check 401'd on `HEAD /?enterAgree=1` even with valid login cookies. Root cause is the combination of (1) gallery-dl's HF extractor checking `self.cookies.get("PHPSESSID", domain="www.hentai-foundry.com")` with `requests`' EXACT domain matching, and (2) the extension's cookies.js forcibly rewriting every captured cookie to a leading-dot subdomain-wide form. HF's PHPSESSID is browser-stored as host-only on `www.hentai-foundry.com`; the rewrite re-anchored it to `.hentai-foundry.com`, which `cookies.get(...)` no longer matches even though the cookie is still sent on actual HTTP requests (RFC 6265 subdomain rules). The extractor falls into its unauthenticated `?enterAgree=1` fallback, which 401s (Cloudflare or HF's anti-bot HEAD gating). Two-part fix, no operator action required for existing stored cookies: 1. **Backend** (`credential_service._augment_cookies`) — refactored from the subscribestar-only single function into a per-platform dispatcher. New `_augment_hentaifoundry` parses the materialized netscape file and, for each `.hentai-foundry.com` entry whose name is PHPSESSID or YII_CSRF_TOKEN, appends a host-only duplicate (`www.hentai-foundry.com\tFALSE\t...`). Originals preserved. Three new tests pin: injection fires + originals preserved; idempotent when host-only already exists; doesn't touch unrelated cookies (e.g. `_ga`). 2. **Extension** (`cookies.js`) — `toNetscapeFormat` now respects `c.hostOnly` from the browser instead of blindly forcing a leading-dot subdomain-wide form. Host-only cookies are written with the bare host + FALSE flag; non-host-only cookies retain the leading-dot + TRUE form. Forward-compat — fresh captures from v1.0.5+ no longer need the backend's host-only duplication. Extension bumped 1.0.4 → 1.0.5; manifest + package.json in lockstep. After deploy: the next HF source check on the operator's already-stored cookies will succeed because the materialized cookies.txt now contains host-only PHPSESSID. No browser re-export needed.	2026-05-27 19:12:51 -04:00
bvandeusenandClaude Opus 4.7	c1d3046778	fc3g(ext): cookies extraction + FC backend API client ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 23:33:26 -04:00
bvandeusenandClaude Opus 4.7	9b01b19666	fc3g(ext): platform registry + artist-page URL patterns ... Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 23:32:47 -04:00