Skip to content

Track ordered NanoBot updates after the July ancestry bridge #13

Description

@dajiaohuang

NanoBot upstream history is connected through 053722a2a2722e846d68562519bfbb4bc1b8c393 by #10. This issue tracks the remaining updates through the pinned upstream revision b9e7c7f6fe67253fecc387df49604ae40e4bc6b4 as small, ordered, reviewable pull requests.

This is a selective semantic integration, not a blanket merge. Each batch must preserve SagaSmith's authoritative MCP boundaries, hosted worker behavior, Local Agent Kit contract, package identity, and Apache-2.0 licensing/third-party notices.

Ordered batches

  • Security and correctness equivalence
  • Session persistence and recovery
  • Agent lifecycle, streaming, and reasoning behavior
  • MCP readiness and OAuth lifecycle
  • Channel package updates in bounded waves
  • Portable plugin support
  • WebUI functional slices
  • Provider updates
  • Native TUI and Herdr integration review
  • Usage, retrieval, and subagent concurrency improvements

Per-PR acceptance gate

  • Pin and cite the exact upstream commit(s) included.
  • List reviewed upstream commits intentionally skipped or deferred.
  • Adapt behavior to SagaSmith rather than overwriting product-specific contracts.
  • Add or update focused regression tests.
  • Run the full relevant Python, WebUI, and distribution checks for the changed surface.
  • Keep licensing and third-party attribution intact.
  • Use a separate PR for dependency-only upgrades or unrelated cleanup.

Current batch

Completed foundations

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions