portal

T

Deploy / deploy (push) Successful in 28s

Details

Fix get_resource/transition_answer: scope feature lookup to its own alternative

Both resolved a feature by name flattened across every alternative on
the question, not scoped to the one the caller actually meant - fine
when every question had exactly one alternative with a resource
feature, silently wrong now that /review has three (Applicants,
Inquiries, Subscribers all use the same empty feature name). Every
lookup always resolved to the first alternative's feature - Subscribers
was reading the (empty) Applicants bucket instead of its own, and
Invite/Decline/Mark-handled buttons would have had the same problem
had two of those transitions ever been clicked side by side.

Threaded a new `alternative` parameter through get_resource,
transition_answer, and their client-side callers
(ResourceFeature/ResourceValue/AnswerRow) - the fix lives entirely in
the already-generic resource-fetching machinery, no per-alternative
special-casing.

2026-08-05 15:04:02 +02:00

.gitea/workflows

Add prosekit rich-text field, Gitea repo embeds, automation KV read endpoint; fix apex/www session-cookie mismatch on /auth/callback

2026-08-05 13:45:56 +02:00

public

Initial commit: content-driven onboarding portal

2026-07-29 19:38:40 +02:00

src

Fix get_resource/transition_answer: scope feature lookup to its own alternative

2026-08-05 15:04:02 +02:00

style

Fix hero-canvas navigation race; style the prosekit editor and add a toolbar