@@ -0,0 +1,21 @@
+# Create publishable Buddy module skeleton
+
+Status: ready-for-agent
+Type: AFK
+
+## Description
+
+Create the new `sentry-android-buddy` Android library module so later Buddy recording code has a proper SDK home. The module should build with the repo's Android library conventions, participate in local Maven publication, expose experimental public API status in the same style as existing Sentry modules, and stay out of the Sentry BOM.
+
+## Acceptance criteria
+
+- [ ] `sentry-android-buddy` is included in the Gradle build as an Android library module.
+- [ ] The module namespace is `io.sentry.android.buddy`.
+- [ ] The module follows existing Android integration module conventions for Kotlin, explicit API, test build type, variant disabling, lint, and dependencies.
+- [ ] The module is locally publishable through the existing Maven Local workflow.
+- [ ] `sentry-android-buddy` is added to Android artifact build config where needed.
+- [ ] `sentry-android-buddy` is explicitly excluded from `sentry-bom`.
+- [ ] Public Buddy APIs can use `org.jetbrains.annotations.ApiStatus.Experimental`.
+- [ ] A minimal smoke test or equivalent focused Gradle validation can run for the module.
+
+## Comments
@@ -0,0 +1,21 @@
+# Add versioned recording format and JSON serializer
+
+Status: ready-for-agent
+Type: AFK
+Blocked by: 01
+
+## Description
+
+Add the public Buddy recording model and deterministic JSON serializer for the first version of the `sentry.mobile_flow_recording` artifact. The schema should represent developer intent, recording metadata, app/device metadata, summary information, normalized timeline items, and Sentry correlation data without depending on UI, backend ingest, or SDK callback interception.
+
+## Acceptance criteria
+
+- [ ] The public recording model represents flow intent, recording metadata, app metadata, device metadata, summary stats, timeline items, and Sentry correlation.
+- [ ] The top-level artifact serializes `type = sentry.mobile_flow_recording`, `version = 1`, `platform = android`, and `useCase = onboard_new_flow`.
+- [ ] Timeline item types include `recording_started`, `screen`, `step`, `breadcrumb`, and `recording_stopped`.
+- [ ] The MVP serializer supports `recording_started`, `screen`, `step`, and `recording_stopped` items; `breadcrumb` is reserved for later.
+- [ ] Serialization uses explicit field ordering and does not rely on reflection.
+- [ ] Public model/serializer APIs are marked `@ApiStatus.Experimental`.
+- [ ] Tests assert representative stable JSON shape and timeline ordering.
+
+## Comments
@@ -0,0 +1,24 @@
+# Implement recorder lifecycle and Sentry correlation
+
+Status: ready-for-agent
+Type: AFK
+Blocked by: 02
+
+## Description
+
+Implement the core Buddy recorder lifecycle around the v1 recording model. The recorder should support one active flow recording at a time, explicit developer steps, summary derivation, Buddy-owned Sentry tags, and a root Sentry transaction that anchors the recording window.
+
+## Acceptance criteria
+
+- [ ] Starting a recording creates a recording ID, records flow intent, records `recording_started`, and enters active state.
+- [ ] Starting a second recording while one is active fails deterministically.
+- [ ] Recording a step while active appends a `step` timeline item with elapsed time and optional data.
+- [ ] Recording a step while inactive fails deterministically.
+- [ ] Stopping a recording appends `recording_stopped`, derives summary data, exits active state, and returns `BuddyFlowRecording`.
+- [ ] Starting a recording sets Buddy scope tags under `sentry.buddy.*`.
+- [ ] Starting a recording starts a root transaction named `Sentry Buddy Recording: <flow_slug>` with operation `ui.flow_recording`.
+- [ ] Stopping a recording finishes the root transaction and removes Buddy's known scope tags.
+- [ ] Sentry correlation fields include available trace/span identifiers from the root transaction.
+- [ ] Tests cover lifecycle, one-active-recording behavior, deterministic failures, summary derivation, Sentry tag calls, transaction finish, and tag cleanup through fakes.
+
+## Comments
@@ -0,0 +1,22 @@
+# Add Android lifecycle collector and public facade
+
+Status: ready-for-agent
+Type: AFK
+Blocked by: 03
+
+## Description
+
+Expose Buddy through a tiny public facade and connect the recorder to Android Activity lifecycle callbacks. Developers should be able to explicitly install Buddy with an `Application`, start a recording, record steps, stop the recording, and get screen timeline items from Activity resumes during the active recording window.
+
+## Acceptance criteria
+
+- [ ] `SentryBuddy.install(application)` registers Buddy's Activity lifecycle collector.
+- [ ] `SentryBuddy.startRecording(intent)` delegates to the recorder and starts a recording.
+- [ ] `SentryBuddy.recordStep(name, data)` delegates to the active recorder.
+- [ ] `SentryBuddy.stopRecording()` returns the finished `BuddyFlowRecording`.
+- [ ] Activity resume events append `screen` timeline items only while a recording is active.
+- [ ] Installing Buddy is explicit; no manifest auto-init is added.
+- [ ] Public facade APIs are marked `@ApiStatus.Experimental`.
+- [ ] Tests cover facade delegation and Activity resume screen collection behavior.
+
+## Comments
@@ -0,0 +1,20 @@
+# Validate local artifact consumption workflow
+
+Status: ready-for-agent
+Type: AFK
+Blocked by: 04
+
+## Description
+
+Validate the new Buddy module as a local Hackweek artifact. The result should be buildable, testable, API-dumped, and locally publishable for external sample-app consumption without adding Buddy to the Sentry BOM or treating it as a stable SDK module.
+
+## Acceptance criteria
+
+- [ ] The focused module test task runs successfully.
+- [ ] Formatting and API dump generation are run for the new public APIs.
+- [ ] The generated API dump reflects the experimental Buddy public API.
+- [ ] Maven Local publication for `sentry-android-buddy` is validated if practical.
+- [ ] Buddy remains excluded from `sentry-bom`.
+- [ ] Any command needed by an external sample app to consume the local artifact is documented in a suitable local artifact or module README if needed.
+
+## Comments