openpond-sdk 0.8.2 → 0.9.1

package/README.md

@@ -330,3 +330,20 @@ pnpm release:sdk:patch
 ```
 
 That command creates an SDK-only release PR. Merging it triggers `release-sdk.yml`; desktop and CLI releases continue to use the existing `pnpm release:patch` command and workflow.
+
+### Independent acceptance evidence
+
+`training.acceptanceGroups({ teamId, jobId }, { cursor, limit })` lists retained
+independent-check groups for an authorized training Job. Pages contain bounded
+summaries rather than complete retry histories. Follow `nextCursor` to read more.
+
+`training.acceptanceGroup({ teamId, jobId }, groupId, reference?)` reads and verifies
+the complete group manifest, checks and attempt history. Passing a summary's
+`{ id, revision, contentHash }` reads that exact retained revision; omitting the
+reference reads the current snapshot. The client verifies workspace/Job/group
+identity and all snapshot hashes. Use `acceptanceGroupVerdict` from
+`@openpond/evals/learning` for the per-check view of verified retained evidence.
+
+These methods only read evidence. They do not dispatch checks, bypass server-side
+acceptance, start training or activate serving. An empty page means this Job has
+no recorded independent group; its existing trainer validation is separate.

package/TRAINING_PROTOCOL.md

@@ -248,3 +248,18 @@ the Taskset and training bundle.
 `createTrainingClient().publishHarnessSource(sourcePackage)` publishes a verified, portable, policy-visible `@openpond/harness` source package to the authenticated workspace without starting a Job. `getHarnessSource({ id, contentHash })` retrieves and verifies that exact release. The endpoints are `PUT` and `GET /v1/training/harness-sources/:releaseId/:contentHash`; they use the existing Training media type and read/write scopes.
 
 Hosted learning resolves this immutable source with Desktop closed. Publish before selecting the release on a hosted Model. Preparation still checks the Taskset adapter, required tools, private grading boundary and effective context; publication is not training or quality qualification. Existing prepared Jobs retain their captured source when a newer release is published.
+
+## Project Profile source binding
+
+SDK 0.9 requires `profileRepositoryId` on Training Project `harness` and `suite`
+targets. This is the authorized hosted repository locator; `source.profileId`
+is the Profile name inside that repository and must not be used as a repository
+ID. Keep both identities through preparation and execution. Existing incomplete
+Profile selections must be reselected explicitly; model targets are unchanged.
+
+Suite sources must contain unique definitions from one exact Profile source,
+catalog and Harness release. Their environment hashes may differ. A host must
+resolve the repository under the caller's workspace/permissions, verify the
+internal Profile ID and all selected immutable identities, and fail admission
+when they no longer match. Project association does not grant repository access
+or permission to execute a Profile's connected applications.