Add ab-av1 worker websocket and shared CRF claiming

.gitignore

@@ -46,3 +46,5 @@ config/dev.overrides.exs
 .expert/
 
 .envrc
+
+.serena/cache/

.serena/memories/conventions.md

@@ -0,0 +1,8 @@
+# Conventions
+
+- Use existing state-machine helpers for video state transitions when available.
+- Treat `:encoded` videos as protected during sync; do not reset encoded state or discard chosen VMAF/original-size data.
+- `Reencodarr.AbAv1.OutputParser` is the shared parser for ab-av1 output; keep encode and CRF-search parsing aligned there.
+- `Reencodarr.Rules.build_args/4` is the central encode/CRF-search argument builder.
+- Service clients live under `lib/reencodarr/services/` and follow existing CarReq retry/fuse patterns.
+- Paginated list LiveViews use URL params plus `ReencodarrWeb.Live.FlopList`; list APIs return `{items, %Flop.Meta{}}`.

.serena/memories/core.md

@@ -0,0 +1,8 @@
+# Core
+
+- Phoenix app for Reencodarr media transcoding; web modules under `lib/reencodarr_web`, domain modules under `lib/reencodarr`.
+- SQLite via `Reencodarr.Repo`; keep DB tuning centralized in `config/config.exs`.
+- Broadway/local worker supervisors are disabled in tests via `config :reencodarr, env: :test` and `Application.worker_children/0`.
+- Existing app invariants and live-debug commands live in `AGENTS.md`; prefer repo evidence, logs, diagnostics, and tests over guessing.
+
+Related memories: commands in `mem:suggested_commands`, done gates in `mem:task_completion`, style in `mem:conventions`, stack in `mem:tech_stack`.

.serena/memories/memory_maintenance.md

@@ -0,0 +1,33 @@
+# Memory Maintenance
+
+## Discovery Model
+
+- Core principle: progressive discovery through references, building a graph of memories.
+- Initially, agents are provided with the list of all memories (names only).
+- Agents should read `mem:core` as the top-level entry point (graph root).
+  This memory should contain references to other memories covering major project domains.
+  The referenced memories shall, in turn, shall contain references to even more specific memories, and so on.
+  The depth of the graph shall depend on the project complexity.
+- Use topics/folders to group related memories in order to make the content structure explicit.
+  Folders can mirror project structure (e.g. modules like frontend/backend) or topics like debugging, architecture, etc.
+- Memory references must use a mem: prefix inside backticks, e.g. `mem:frontend/core`.
+  The surrounding text should clearly indicate when to read the memory/which content to expect.
+  The text should provide more precise guidance than the memory name alone, 
+  i.e. avoid a reference like "frontend debugging: `mem:frontend/debugging` and instead make clear which aspects of frontend debugging are covered.
+- Memories themselves should not contain information about when to read them; this is the responsibility of the referring memory.
+
+## Style
+
+Dense agent notes, not prose docs. Prefer invariants, terse bullets. 
+Avoid obvious context, rationale, and examples unless they prevent likely mistakes. 
+Keep guidance durable and generalizable, not task-local.
+
+## Add/update threshold
+
+Add or update memories only with stable, non-obvious project conventions that avoid complex rediscovery in the future.
+Do not add: quick-read facts; generic language/framework knowledge; one-off task notes; volatile line-level details; behavior likely to change soon.
+
+## Maintenance Actions
+
+- Renaming memories: References are updated automatically if handled via Serena's memory rename tool.
+- Checking for stale memories (e.g. after deletion): Call `serena memories check` for a report.

.serena/memories/suggested_commands.md

@@ -0,0 +1,9 @@
+# Suggested Commands
+
+- `nix develop -c mix setup` installs deps, creates/migrates DB, and builds assets.
+- `nix develop -c mix test` runs the full test suite.
+- `nix develop -c mix test path/to/test.exs` runs focused tests.
+- `nix develop -c mix compile --warnings-as-errors` catches compile regressions.
+- `nix develop -c mix credo --strict` runs lint.
+- `nix develop -c mix format` formats; `nix develop -c mix format --check-formatted` verifies formatting.
+- `bin/rpc 'Reencodarr.Diagnostics.status()'` and sibling diagnostics helpers inspect the running system.

.serena/memories/task_completion.md

@@ -0,0 +1,6 @@
+# Task Completion
+
+- Prefer focused tests while iterating, then run broader gates when practical.
+- Standard finish gates: `nix develop -c mix test`, `nix develop -c mix compile --warnings-as-errors`, `nix develop -c mix credo --strict`, and `nix develop -c mix format --check-formatted`.
+- Run `nix develop -c mix format` before committing Elixir changes if formatting may have changed.
+- For live runtime/debug claims, verify with `bin/rpc` diagnostics rather than inferring from source.

.serena/memories/tech_stack.md

@@ -0,0 +1,8 @@
+# Tech Stack
+
+- Elixir `>= 1.20.0 and < 1.21.0` Phoenix app.
+- Phoenix `~> 1.8.8`, LiveView `~> 1.2.5`, Bandit `~> 1.12`.
+- SQLite through `ecto_sqlite3`/`exqlite`; Ecto SQL `~> 3.14`.
+- Uses Nix dev shell for repo commands: `nix develop -c ...`.
+- Assets use Tailwind package `~> 0.5.1` and esbuild `~> 0.10` via Mix aliases.
+- Test helpers include ExUnit, ConnCase/DataCase, StreamData, Floki/LazyHTML, and meck where existing tests mock external commands.

config/runtime.exs

@@ -20,6 +20,27 @@ if System.get_env("PHX_SERVER") do
   config :reencodarr, ReencodarrWeb.Endpoint, server: true
 end
 
+worker_token =
+  System.get_env("REENCODARR_WORKER_TOKEN")
+  |> case do
+    nil ->
+      case System.get_env("SECRET_KEY_BASE") do
+        nil ->
+          nil
+
+        secret_key_base ->
+          :crypto.mac(:hmac, :sha256, secret_key_base, "ab-av1-worker-token")
+          |> Base.url_encode64(padding: false)
+      end
+
+    worker_token ->
+      worker_token
+  end
+
+if worker_token do
+  config :reencodarr, :worker_token, worker_token
+end
+
 if config_env() == :prod do
   # Parse CHECK_ORIGIN env var: "false" disables, otherwise comma-separated origin list
   parse_check_origin = fn