Skip to content

Preserve shared-turn context and verify task creation (JVNAUTOSCI-2739) - #610

Merged
witbrock merged 1 commit into
mainfrom
fix/JVNAUTOSCI-2739-shared-turn-context
Sep 11, 2026
Merged

witbrock merged 1 commit into
mainfrom
fix/JVNAUTOSCI-2739-shared-turn-context

Conversation

@witbrock

Copy link
Copy Markdown
Member

Outcome

Shared turns retain accepted participants, exact speaker identities, and the source actor/org scope of historical observations. Task creation is treated as a valid outcome, separate from executing the work recorded in a task.

Smallest adequate changes

  • Project server-derived participant/current-scope metadata and historical author/tool provenance into provider-visible text. Preserve canonical history and existing access filters; do not turn conversation participation into task or identity authority.
  • Return an explicit verified task-record receipt alongside the unchanged legacy canonical read-back row. Pending lifecycle status no longer makes a successful create appear unverified; no task execution is asserted.
  • Check exact fresh read-back identity and reject incomplete retry records without creating duplicates.
  • Describe existing self-assignment and record-only task semantics accurately. No new intent classifier, workflow layer, automatic assignment, or global model routing change.

Validation and release decision

Merge decision changes — ready, subject to required CI. 122 affected-path tests and 25 focused adaptive-turn tests pass. New-file Ruff, affected-file fatal Ruff and diff checks pass. Coverage includes accepted/pending/revoked/foreign participants, no profile lookup for nonparticipants, preserved source history, actual provider text projection, window scope, private-task denials, verified pending records, partial/wrong-ID read-backs, and retry reconciliation.

Three bounded synthetic gpt-5.6-luna checks proposed a fresh exact task read after a scope change, proposed only task creation for an explicit task-only request, and resolved participant IDs correctly. Tool proposals were not dispatched. These are bounded observations, not a guarantee for arbitrary prompts.

No real user tasks, messages, authority grants, or deployments changed. Stop-ship conditions are leaked private metadata, lost source text, changed authority, or falsely verified task creation.

Tracking: https://naoinstitute.atlassian.net/browse/JVNAUTOSCI-2739

@witbrock
witbrock merged commit 57e5c29 into main Sep 11, 2026
2 checks passed
@witbrock
witbrock deleted the fix/JVNAUTOSCI-2739-shared-turn-context branch September 11, 2026 03:41
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