Extension probe-and-add (v1.0.6) + per-commit image tags #40
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Two coupled landings:
d65f0b2— Extension probe-and-add (v1.0.6)Operator-asked 2026-05-31. The extension's floating button now reflects the URL's actual state in FC BEFORE the click instead of learning it after:
✓ In FabledCurator · Patreon→ click opens the FC artist page in a new tab (operator's pick).+ Add Patreon source to {artist}→ click adds a new Source against the existing artist. Covers the sidecar-synthetic-only "Dymkens" case from v26.06.01.0.+ Add to FabledCurator→ click creates artist + source (current behavior)./posts/N,/home, etc.).New
GET /api/extension/probe?url=...read-only backend route +ExtensionService.probe. Extension v1.0.5 → 1.0.6 so build.yml'sext-1.0.6cache miss fires AMO sign-extension and exercises the regenerated AMO keys end-to-end. 6 backend tests covering all states + auth + invalid URL.8de7ccd—:c-<short_sha>per-commit image tagsImplements the new family release-posture rule (Scribe rulebook rule #46): every main-push build now publishes
git.fabledsword.com/bvandeusen/fabledcurator{,-ml}:c-<short_sha>alongside the floating:main/:latest. Rollback to any commit on main isdocker pull …:c-<sha>— no release ceremony required.vYY.MM.DDtags become opt-in milestone labels (no.Nsuffix); tag-push workflow stays as a no-op when you choose to mark one.Test plan
:main,:latest,:c-<short_sha>)./artist/<slug>in a new tab.ext-1.0.6) and the AMO round-trip succeeds — exercises the regenerated keys end-to-end.Adds an immutable per-commit docker tag to every main-push build: `git.fabledsword.com/bvandeusen/fabledcurator{,-ml}:c-<short_sha>`, alongside the existing floating `:main` + `:latest`. Implements the new family release-posture rule "Tags are milestones, not gates — commit-SHA images are the rollback unit" so rollback to any commit on main is `docker pull …:c-<sha>` with no release ceremony required. Behavior change summary: - main-push: was {:main, :latest} → now {:main, :latest, :c-<short_sha>} - tag-push (opt-in vYY.MM.DD only, no .N): unchanged - safety-net dev: unchanged No code changes; the rule is about how the tag list is constructed. Tag-push workflows stay as-is — vYY.MM.DD milestone cuts can still fire them when the operator wants a labeled checkpoint.