fix(spa): render every ModelAdmin.actions entry on detail page (#618, #619) + release 1.4.11

[MartinCastroAlvarez]

Closes #618, closes #619.

#618 — drop the over-narrow detail-page filter

The 1.4.9 object_actions.filter(target === 'detail') filter dropped every batch-classified action on the floor. Since the stock Django pattern is @admin.action(description=...) with (modeladmin, request, queryset) — i.e. target: 'batch' — virtually every consumer's actions were invisible on the detail page. That contradicted the documented "one @admin.action → two surfaces" contract.

Fix: render every entry in object_actions. The action runner endpoint already dispatches both shapes correctly — batch as action(modeladmin, request, queryset_of_one) against the detail page's single pk, detail as action(modeladmin, request, str(pk)). Both work; the filter was the bug.

- {(data.object_actions ?? [])
-   .filter((action) => action.target === 'detail')
-   .map(...)}
+ {(data.object_actions ?? []).map(...)}

#619 — README copy matches the corrected behaviour

Rewrote the "Add custom admin actions" section. The default example is now the stock (modeladmin, request, queryset) shape (it now correctly renders on both surfaces); the detail-only signature is documented as the optional second path. The previous copy implied an exclusive split (batch → changelist-only) — that mental model is what produced #618.

Verification

• pnpm -r typecheck ✓
• pnpm lint (js + css + darkmode coverage) ✓
• pnpm test — 163 / 163 ✓
• pnpm -w build ✓

Not in this PR

• SPA action runner: HttpResponseRedirect from a ModelAdmin action is silently swallowed — "Download <thing>", "View HTML", "Hijack" all break #620 (HttpResponseRedirect swallowed by the action runner). Bigger fix — needs a response classifier (JSON / 3xx / HTML / binary) plus possibly an API-side envelope to expose redirect targets through redirect: "manual"'s opaque response. Tracked for the next release.

🤖 Generated with Claude Code