Link a finished timelapse to a devlog (reassure + attach)

[dhamariT]

The problem

People think their Lookout recording vanished. After recording, the timelapse is saved on Stardance's side — but it never surfaces again and isn't tied to anything, so it feels lost.

Digging in: the backend already supports linking a session to a devlog (DevlogsController#attach_lookout_sessions reads params[:post_devlog][:lookout_session_ids]), but nothing in the UI ever sends it, and devlogs never display a timelapse. So the wiring exists — it's just not connected.

This PR — "reassure + link first" (flag: timelapse_devlog, off by default)

1. Recorder done screen: says it plainly — "Saved! We've got your timelapse" — and turns "Post a Devlog" into "Add it to a devlog", carrying the session id + just_recorded=1 back to the project page.
2. Project page (ProjectsController#show): reads lookout_session_id, sets @pending_lookout_session (must be attachable, owned by the user, not already linked).
3. Composer: renders a hidden post_devlog[lookout_session_ids][] for that session + a reassurance banner ("Your timelapse (Xm) is saved and will be attached to this devlog"). The modal controller auto-opens the composer on ?just_recorded=1 and strips the params.
4. Devlog card: a small "Timelapse attached" chip when the devlog has a linked session — so the connection is visible on the post.

Backend link + the destination flow are unchanged; on submit the existing attach_lookout_sessions sets devlog_id.

Turning it on (and rolling back)

The whole feature is gated on the timelapse_devlog Flipper flag, registered in config/initializers/flipper.rb. It's a per-actor flag (Flipper.enabled?(:timelapse_devlog, current_user)), so you can enable it for yourself first, then a percentage, then everyone. Enable it the same way as lookout.

Heads up: the flag gates both sides — the author flow (recorder → "Add it to a devlog") and the viewer's "Timelapse attached" chip. So test with the flag enabled for the user who records and views.

Option A — Flipper UI (/admin/flipper, admin-gated):

• Go to https://stardance.hackclub.com/admin/flipper, open timelapse_devlog.
• Just you: under Actors, add your user's flipper_id and register it.
• Gradual: set Percentage of Actors (e.g. 10 → 50 → 100).
• Everyone at once: flip the Boolean gate to fully on.
• Roll back: clear the gate(s) / toggle Boolean off.

Option B — Rails console (Coolify web or worker, bin/rails console):

# just one user (recommend starting here — enable it for yourself)
Flipper.enable_actor(:timelapse_devlog, User.find(<your_user_id>))

# gradual rollout to a % of users
Flipper.enable_percentage_of_actors(:timelapse_devlog, 25)

# everyone
Flipper.enable(:timelapse_devlog)

# roll back / turn fully off
Flipper.disable(:timelapse_devlog)

Prod is byte-for-byte unchanged until you enable it for an actor.

Deliberately deferred (fast follow)

The actual timelapse frame as the devlog's image (auto-attaching a screenshot). Lookout exposes a thumbnailUrl; the plan is a same-origin thumbnail proxy + pre-attach into the composer so the screenshot shows in the draft.

Notes / tradeoffs

• Reuse-only: no new endpoints, models, or migrations. Uses the existing attachable scope, format_seconds helper, the modal query-param opener pattern, and BEM classes in _feed.scss.
• The card chip does a per-card lookout_sessions.exists?; gated behind the flag to bound cost during rollout. Preload lookout_sessions on the timeline query before this goes wide (follow-up).

Testing

• ruby -c / ERB parse / node --check all clean.
• Manual (with :timelapse_devlog on): record a timelapse → "Add it to a devlog" → project page opens the composer with the reassurance banner + hidden session field → post → devlog shows the "Timelapse attached" chip and the session's devlog_id is set.

---

Note

Medium Risk
Touches devlog create params and session linking with Flipper gating; card exists? queries may need preload before wide rollout, but behavior is unchanged until the flag is enabled.

Overview
Under the timelapse_devlog Flipper flag (off by default), this connects the existing devlog attach path (post_devlog[lookout_session_ids][] → attach_lookout_sessions) to the UI so finished Lookout sessions don’t feel lost.

Author flow: After recording, the done screen becomes “Add it to a devlog” with copy that the timelapse is saved, linking to the project with lookout_session_id and just_recorded=1. ProjectsController#show loads a linkable session (new scope: stopped / compiling / complete, broader than attachable) owned by the user and not yet linked. The devlog composer shows a reassurance banner plus a hidden session id field; modal_controller opens the composer on ?just_recorded=1 and strips only that param (keeps lookout_session_id for refresh-before-submit).

Feed: Devlog cards show a mint “Timelapse attached” indicator when the post has linked lookout sessions (flag-gated; uses lookout_sessions.exists? per card).

Styling adds composer note and card timelapse chip classes in _feed.scss. No new endpoints or migrations.

^{Reviewed by Cursor Bugbot for commit eb3dd94. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit eb3dd94. Configure here.}

[cursor]

Project chip drops timelapse link

Medium Severity

After recording, the composer keeps a hidden post_devlog[lookout_session_ids][] for the timelapse and tells the user it will attach, but the project-page composer still shows project chips. Choosing another chip retargets the form to that project’s devlogs endpoint while the hidden id still refers to a session scoped to the original project, so attach_lookout_sessions finds no row and the timelapse is not linked.

 

^{Reviewed by Cursor Bugbot for commit eb3dd94. Configure here.}