Accept inline artifact-ignore patterns via message protocol

[jackcbrown89]

Summary

• Add optional artifacts_ignore_content?: string to InvocationMessage and CommandExecutionMessage so consumers can carry gitignore-format ignore patterns through the wire instead of relying on a .artifactignore file at the watched directory.
• ArtifactManager.addDirectory(dir, options?) now resolves patterns in this order:
  1. options.ignoreContent if provided (pinned — runtime file events for .artifactignore no longer overwrite it).
  2. <dir>/.artifactignore on disk (existing behavior, kept for back-compat).
  3. DEFAULT_ARTIFACT_IGNORE, with a logger.warn so the fallback is visible in operator logs instead of silently masking a misconfig.
• Python client: new artifacts_ignore_content field on QueryOptions and ExecuteCommandsOptions, plumbed through both invocation and command-execution message builders.
• Bump both packages to 0.15.0.

Why

Consumers whose watched directory is created (or wiped) by the runtime environment after image build time can't ship a .artifactignore reliably — by the time the runtime starts watching the directory, any file copied at build time may be gone. Routing the patterns through the message protocol removes that filesystem-coupling. Promoting the previously-silent default fallback to a warn makes future regressions of this kind visible immediately.

Test plan

• npm run typecheck (clean)
• npm test — 159/159 vitest tests pass, including new coverage for: inline-blob match/skip, blob-vs-file precedence, file events not overwriting the inline blob, the new warn on the default fallback, and session forwarding of artifacts_ignore_content to every addDirectory call (invocation + command-execution).
• uv run pytest test/test_client.py — 61/61 pass, including new round-trip tests for artifacts_ignore_content on both query and execute_commands.
• Existing-consumer back-compat: a message with only artifacts_dirs (no artifacts_ignore_content) and a .artifactignore at the watched dir continues to load the file (covered by existing tests, which still pass).

---

Note

Medium Risk
Changes the artifact-watching/ignore-path behavior and message schema, which could impact which files are uploaded and how existing .artifactignore setups behave if edge cases were missed.

Overview
Adds optional artifacts_ignore_content to invocation and command-execution messages so clients can supply gitignore-style artifact ignore rules over the wire instead of relying on an on-disk .artifactignore.

Updates the runtime ArtifactManager to accept per-directory ignoreContent, pinning in-memory patterns so .artifactignore file events don’t overwrite them, and emits a warn when falling back to the built-in default ignore rules. The session layer now forwards artifacts_ignore_content (treating null as omitted) to every addDirectory call, and the Python client plumbs the new option through QueryOptions/ExecuteCommandsOptions with added tests.

Bumps runtimeuse and runtimeuse-client versions to 0.15.0.

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

[cursor]

Cursor Bugbot has reviewed your changes 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 265bcc9. Configure here.}