chore(release): 1.10.0 + OpenSpec record of team-aware recall surface changes

[GQAdonis]

Summary

• OpenSpec change team-aware-recall-surfaces. It records the frozen-surface changes that merged in fix(context): score every snapshot entry before applying the candidate cap #31, fix(worker): attribute learning to project/team/role and commit the prompt snapshot #32 and feat(ingest,context): --type and --tag on ingest, --tag filter on context #34 without the OpenSpec change this repo requires:

  • pk context --format json: scoring changes, a new scored_count, and a changed meaning for candidate_count;
  • pk context --tag;
  • pk ingest --type/--tag;
  • attributed learning jobs.

  The change names each consumer and explains the updated assertion in the contract test pk-cli/tests/context.rs (see design.md).

• Release gate evidence (design.md). The 1.9.0 WikiEntry.sources break is covered by compatibility shims: with_sources accepts Into<Source>, From<String> and From<&str> exist, and deserialization reads both the string and mapping forms. No known consumer reads the field directly. Whether that satisfies the "no tag while a break is unresolved" rule is the maintainers' decision. Task 4.2 stays unchecked until then.

• Version bump. The workspace and its internal dependency pins move from 1.9.0 to 1.10.0. Cargo.lock was refreshed offline, and only workspace members changed.

Test plan (with --locked)

• pk-cli: context 3/3, context_scoring 3/3, tags_and_type 1/1.
• pk-learning-worker: attribution 2/2, worker 5/5.
• The built binaries report pk 1.10.0 and prometheus-learning-worker 1.10.0.
• After merge, and once the maintainers confirm the sources gate: tag v1.10.0 on the merge commit.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.