Skip to content

feat(harness): share context owner across Assistant lifecycle consumers [SAP-3292] - #1019

Closed
ynadge wants to merge 1 commit into
assistant-lifecycle-actionsfrom
assistant-context-consumer
Closed

ynadge wants to merge 1 commit into
assistant-lifecycle-actionsfrom
assistant-context-consumer

Conversation

@ynadge

@ynadge ynadge commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

Primary change type

  • Feature

Problem and motivation

Lifecycle consumers need the same accepted context and verified runtime as ordinary Assistant Send and recovery.

Summary and scope

Add an explicit server-owned context runtime capability and one shared delivery builder. Use the exact host state root for accepted sources, preserve default legacy delivery when absent, append frozen recorded guidance to every child Send, and cancel availability checks before credentials or native launch. Runtime publication, pinning, signing and default activation remain with the Epic 2 owner.

Related work

Related issue: https://linear.app/sapiom/issue/SAP-3292

Depends on #1018. Native stack target: main.

Validation

123 focused tests passed across host, consumer, resolver, delivery and readiness. Harness server build, full server TypeScript, scoped ESLint with zero warnings, formatting and diff checks passed. A cancellation mutation was detected and restored.

Tests and documentation

Real source-store cases cover retained-source recovery after engine deletion, source loss, legacy inline fallback, inactive capability, fresh current guidance plus frozen child context, and End during availability checks. Updated assistant-history.md. Increment:891 changed lines including tests/docs/changeset; SDK pr:size is absent.

Compatibility and release impact

  • Safe initial state: capability absent, existing legacy delivery retained, Continue fails before allocation. Owner: existing context runtime delivery owner; enable only with its verified launcher/capability. Remove transitional fallback when that owner's activated runtime is the supported default. Both capability states are tested.
  • Changeset: @sapiom/harness patch.
  • Fix-forward: withdraw the injected activation capability and correct the shared consumer while preserving accepted source ownership and receipt identity.

Security

  • No secrets, credentials, private data, or unsanitized logs included.
  • No suspected vulnerability disclosed publicly.

AI assistance

  • AI assistance used: Codex implemented and reviewed the change with the validation described above.

Checklist

  • CONTRIBUTING.md read; maintainer-authorized issue work.
  • One focused increment, checks, documentation and release impact addressed.
  • I can explain and maintain the submitted changes.

Devin Review

@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 290d28c9-f6e3-4706-bdbb-6bc7c42981af

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant