Skip to content

Resolve planning feedback to existing scoped proposals instead of reconstructing IDs #341

Description

@adrianwebb

Objective

Unblock real work/review acceptance in Platform #501 / SDK #293. Human-created proposal 48d5429f-4882-4e89-824e-1866e70e7adb has a UUID, while planning feedback currently reconstructs proposal::, rejecting existing human-authored proposals.

Contract

Resolve an existing proposal by exact ID or its project-scoped content slug; enforce assignment team/project scope, reject ambiguous or missing subjects, and preserve the existing ID. Do not create duplicate proposals, aliases, synthetic reviews or direct database records. Record immutable feedback evidence and the reviewed proposal version; do not count stale feedback against a newer proposal.

Acceptance

  • Regression tests cover human UUID, agent-generated ID, content slug, wrong team/project, missing/ambiguous subject, stale version and idempotent feedback.
  • Required Actions pass; PR merges to current staging, then batched RC and managed acceptance.
  • Actual independent agent feedback attaches to the public API-created SDK proposal before voting/work acceptance.

Dependencies / rollback

Platform #501 and SDK #293. TreeDX18/API107 byte-safe publication is activating. No schema migration; rollback to previous accepted API only before new semantics are relied upon. Preserve all proposal history.

Evidence

Gate Evidence Status
Static defect assignment-planning-output-service.ts feedback loop synthesizes proposal ID Confirmed
Automated / live acceptance Pending Open

Implementation / checks

PR #342 merged a77d57f after required Actions34596654055 (verify),34596687697 (record),34596687690 (authorization) passed. Final head983529616e238790343509a155d7abf50f0588e3;38focused tests pass, full877tests/10existing skips before final3passing structured-review cases; build/architecture pass. Existing project-scoped proposal ID resolution, exact library snapshot, selected subject context and current-version review evidence are implemented. Same source runs through managed live API service/runner; provider and TreeDX remain healthy; fresh source-custody-254 send completed ok.

Release and real independent-feedback/work-candidate acceptance remain open. User choice pending: expose existing targeted agent/activity selection through public SDK/API/CLI or use all30SDK workday planning activities. No fabricated review/decision or recurring-schedule workaround.

Activity

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

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