feat(remote): download ordinary recordings without closing the session - #4511

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/remote/src/daemon-artifacts.ts, line 468:

<comment>`artifact.force` can authorize overwriting a different caller destination during the first export. Preserve the force grant only when it applies to this request’s destination, or have the daemon compute force per caller path.</comment>

<file context>
@@ -447,11 +464,17 @@ export async function materializeRemoteArtifacts(
       // `downloadRemoteArtifact`).
       isDirectory: artifact.artifactType === 'test-artifacts',
+      ...(artifact.artifactType === 'session-script'
+        ? { scriptForce: req.flags?.force === true || artifact.force === true }
+        : {}),
     });
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At docs/adr/0016-active-session-script-publication.md, line 91:

<comment>This exception contradicts the unchanged failure list in the Artifact contract ("The recording is ABORTED or PUBLISHED") and the validation bullet "a repeated `session save-script` fails". Update those statements and the Rules at a glance so the remote PUBLISHED re-download case is stated once, consistently.</comment>

<file context>
@@ -88,7 +88,11 @@ An ordinary recording eligible for active-session publication has three states:
 Thus, the caller can correct the target or permissions and retry.
 ABORTED and PUBLISHED are terminal until the session is destroyed.
-In either state, `session save-script` fails with an explicit error and never writes.
+In either state, `session save-script` never records or publishes new script content.
+A PUBLISHED remote recording may return its retained immutable artifact for another caller-side download.
+This exception does not change the terminal recording state.
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At test/integration/provider-scenarios/remote-script-publication.test.ts, line 177:

<comment>This negative check passes for any non-200 status, including a 500 or 404. Assert the auth refusal directly with `assert.equal(denied.status, 401)` so a broken auth gate on `/artifacts/<id>` cannot pass.</comment>

<file context>
@@ -0,0 +1,191 @@
+      assert.ok(artifact?.artifactId);
+      assert.equal(artifact.path, undefined);
+      const denied = await fetch(`${proxy.baseUrl}/artifacts/${artifact.artifactId}`);
+      assert.notEqual(denied.status, 200);
+      const downloaded = await fetch(`${proxy.baseUrl}/artifacts/${artifact.artifactId}`, {
+        headers: { authorization: 'Bearer raw-client' },
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/daemon/src/core/session-action-recorder.ts, line 76:

<comment>The client delivery metadata passed here is dropped when no path is given. `resolveScriptTarget` returns early on `requested.path === undefined` without applying `clientPath` or `remote`, so a bare `--save-script` or `session save-script` over remote never produces a downloadable `session-script` artifact. If remote export should work without an explicit path, carry `clientPath` and `remote` through that early return. If default-target remote export is unsupported, reject it explicitly instead of silently ignoring the flag.</comment>

<file context>
@@ -65,7 +67,14 @@ export function recordActionEntry(
+      entry.flags,
+      hostCwd,
+      entry.clientScriptPath,
+      entry.remoteScriptDelivery,
+    );
   const fillLiteral = readRecordedFillLiteral(entry);
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/daemon-contracts/src/daemon-resolution.ts, line 151:

<comment>This capability addition changes the published `daemon.json` shape and breaks the existing quiesce runtime test, which still expects only `['quiesce']`. Update that assertion (and related fixture expectations) to include `active-script-artifacts`.</comment>

<file context>
@@ -148,7 +148,7 @@ export function resolveDaemonTransportPreference(
 
 /** What a daemon can do beyond the base RPC contract, published in its `daemon.json`. */
-export const DAEMON_CAPABILITIES = ['quiesce'] as const;
+export const DAEMON_CAPABILITIES = ['quiesce', 'active-script-artifacts'] as const;
 export type DaemonCapability = (typeof DAEMON_CAPABILITIES)[number];
 
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/daemon-client/src/daemon-client-rpc.ts, line 217:

<comment>This save-script predicate is now duplicated in `sendHttpRequest` (daemon-client-transport.ts:800). Extract it into one helper, such as `requestNeedsActiveScriptArtifacts(req)`, and call it from both places so the capability gate and the network-access header cannot drift apart.</comment>

<file context>
@@ -207,3 +208,22 @@ export function refuseOversizedDaemonRequest(payload: string, requestId: string
+  if (
+    info.baseUrl &&
+    !info.capabilities?.includes('active-script-artifacts') &&
+    (req.flags?.saveScript || req.command === INTERNAL_COMMANDS.sessionSaveScript)
+  ) {
+    throw new AppError(
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/remote/src/__tests__/daemon-artifacts-script-download.test.ts, line 26:

<comment>The fake server never checks the requested path, so the test would pass even if the client downloaded a different artifact. Assert that `req.url` ends with `/script-id` (or matches the expected artifact route) in the handler.</comment>

<file context>
@@ -0,0 +1,124 @@
+    if (existing) fs.writeFileSync(destination, 'original');
+    const text = 'context platform=ios\nopen Demo\n';
+    const server = http.createServer((req, res) => {
+      expect(req.headers.authorization).toBe('Bearer test');
+      expect(req.headers['x-agent-device-tenant']).toBe('tenant');
+      expect(req.headers['x-agent-device-lease-id']).toBe('lease');
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/daemon/src/sessions/handlers/__tests__/session-script-publication.test.ts, line 376:

<comment>This test's name says it covers regeneration from later actions, but the fixture has no actions after `publishedActionCount: 3`. Add a fourth recorded action after the publication point so the test proves later actions do not regenerate the expired artifact.</comment>

<file context>
@@ -348,3 +348,50 @@ test('refuses mutating find steps that cannot enforce target identity on replay'
+  expect(fs.existsSync(output)).toBe(true);
+});
+
+test('an expired remote publication is not regenerated from later actions', () => {
+  const output = path.join(root, 'expired.ad');
+  store.publish(
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/remote/src/daemon-artifacts.ts, line 496:

<comment>The doc comments above `finishesEarlierClientCapture` and `resolveMaterializedArtifactPath` still describe only stop and report requests as accepting an echoed `localPath`. Update them to cover `session save-script` as well, since this case now accepts it.</comment>

<file context>
@@ -467,9 +490,11 @@ export async function materializeRemoteArtifacts(
+function finishesEarlierClientCapture(req: DaemonWireRequest, artifact: DaemonArtifact): boolean {
   const [first, second, third] = (req.positionals ?? []).map((value) => value.toLowerCase());
   switch (req.command) {
+    case INTERNAL_COMMANDS.sessionSaveScript:
+      return artifact.field === 'savedScript' && artifact.artifactType === 'session-script';
     case 'record':
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/remote/src/daemon-artifacts.ts, line 130:

<comment>Empty `session save-script ""` skips the daemon's `cannot be empty` guard: the client strips the positional and resolves the empty path to the cwd directory. Reject a blank path here before publishing.</comment>

<file context>
@@ -95,25 +97,40 @@ export async function prepareRemoteRequestArtifacts(
+  }
+  clientPaths.savedScript = localPath;
+  if (active) {
+    if (positionals.length === 1) positionals.length = 0;
+    return flags;
+  }
</file context>