Product Manager 4.2.0

4.2.0

Discover the assigned imported software project and retain its project/repository identity. Use the normal CEO direction, staffing and reviewed setup process to adopt it after required roles are available. Recover on project-change hints and attention reviews. Preserve schema-valid discussion cursors with compatibility for legacy scalar cursors.

Requires C-Sweet Agent SDK 5.9.0 and the business-first import platform changes. Deploy through the normal published release and Installed Agents update flow.

Product Manager 4.1.6

4.1.6

Correct retained-stage validation to distinguish platform grants from agent-provided execution
callbacks. The roster's EffectiveCapabilities contains granted platform operations; it does
not advertise work.execution.run. Exact available employee/installation bindings and
independent reviewers remain required. Typed planning and delivery finalization still recheck
the retained installation's current execution eligibility on the platform.

The delivery fixtures now reproduce the live roster shape. They verify faithful adoption and
preparation, rejection of changed principals, and refusal to mutate when the platform denies
current eligibility. No permissions, role changes, review waivers or deployment authority added.

Product Manager 4.1.5

4.1.5

Retain a content fingerprint when saving the bounded ticket-discussion recovery cursor, so the
platform can admit its operating-state record. Restart reconciliation remains bounded and does
not generate replies for informational comments.

The retained-brief adoption and selected-sprint preparation tools now return explicit failed
results for expected validation and broker rejections. Only a successful result carries a
receipt; cancellation and unexpected faults still propagate. Tests invoke the actual tool
binding and exercise recovery state, rejection and cancellation.

No permissions, staffing, review gates, accepted requirements or deployment authority change.

Product Manager 4.1.4

4.1.4

Preserve the existing platform-owned task-integration assignment during retained-brief adoption
and isolated delivery preparation. It must be the canonical task-integration stage and action,
with no employee or installation identity. Author and independent human/agent reviewer checks
remain unchanged. Unknown actions, impersonated principals and duplicate stages fail closed.

The delivery fixtures now include the real platform integration binding. They reproduce its
former rejection and verify both exact preservation and rejection of altered bindings. No
permissions, approvals, integration actions or publication authority are added.

Product Manager 4.1.3

4.1.3

Keep adapter-only planning, finalization and communication reads out of the confined chat tool
request. The SDK continues to reject missing, duplicate or hidden model bindings. Existing typed
adapter operations retain their normal grants and authority checks.

Add adopt_developer_brief for an existing Ready ticket in a Planned sprint on a project and
board currently managed by this employee. It copies the existing complete developer brief
without rewriting requirements, criteria, constraints, owner or retained stage installations.
It fills only a missing employee identity for an exact unique retained installation in the
current roster, preserves independent reviewers and uses revision-checked typed planning.
Existing planning, explicit quality-gate/rework bindings and finalized work cannot be replaced.
No grants, sprint-start, promotion, approval or deployment permissions are added.

Product Manager 4.1.2

4.1.2

Declare two adapter-only read requirements used by existing-project management:
platform.project-assignment.read.v1 supplies the caller's server-resolved assignment, and
platform.workstream.read.v1 verifies current project status and accountable management.
Both remain hidden from model tools and require reviewed installation grants. Existing
participant, management and mutation checks remain in force.

Delivery regression fixtures now register only capabilities declared by the packaged manifest.
They exercise assignment reads, retained-project chat routing and isolated delivery preparation,
including denial before mutations when either project-context read is revoked.

Product Manager 4.1.1

4.1.1

Existing-project manager replies now reach the normal delivery and discussion tools instead of
being consumed by a pre-assignment initial-team staffing commitment. A retained project assignment
also retires that obsolete staffing callback through the normal personal-work result, after current
management checks. Stale management is reported and cannot trigger replacement-team design.

Validation: regression cases cover current and stale management and retain the initial-team path
for managers without a project assignment. No permission or SDK dependency changes.

Product Manager 4.1.0

Product Manager 4.1.0

• Prepare a specifically selected Planned code sprint using accepted ticket scope, exact reviewers and an approved repository. Retain a revisioned delivery receipt and recover interrupted setup without duplicate plans or task finalization.
• Answer directed ticket questions through current authorized discussion reads and correlated comments, retaining generated replies across interrupted writes and rejecting stale or changed evidence.
• Reconcile existing assigned project delivery without creating a replacement team or board. Keep old sprint-readiness callbacks from selecting a successor sprint.
• Add current-discussion read access and its event subscription. Existing platform grants, preflight, independent review, source promotion and deployment controls remain authoritative.

Verification: published-package build and regression suites, manifest identity, package/bundle verification and configured-model behavior checks. Live installation and the governed manager round trip are evaluated separately.

Product Manager 4.0.0

4.0.0

Uses SDK 5.0.2 to publish agent-authored delivery plans as canonical workflow tickets with dependencies and acceptance criteria. Supports the clean-start platform workflow without implicit aggregate review gates. No new grants are requested.

Product Manager 3.1.2

3.1.2

• Default to OnDemand activation so idle agents release Office capacity while durable work wakes them when needed.
• Requires the platform attention scheduler update for sleeping OnDemand installations. Existing installation schedules must be changed separately.