Prepare API rc111 activity-profile closure

[adrianwebb]

Outcome

Prepare 0.8.0-rc.111 as the unique immutable release identity for the merged cross-profile Kata closure.

Work authority

• Work item / Issue: Expose bounded workday agent/activity selection for real review acceptance #344; parent Capacity execution: isolated cached source workspaces and research-capable agents platform#501
• Proposal / decision: User-directed activity-profile Kata acceptance in the current Codex task
• Assignment / checkpoint: Current Codex task; post-merge release checkpoint 2026-09-11
• Actor: Codex
• Human authority: adrianwebb
• Agent / capacity provider: N/A — repository release preparation in the local authorized workspace
• Exact base ref: staging bbf86c2
• Exact head ref: codex/activity-profile-kata-release 59a8b3f

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Assign a new version to the already-verified staging bytes, validate package/lock agreement, pass Actions, merge, then promote the exact protected candidate without rebuilding.

Changes and commits

One bounded version-lock commit prepares 0.8.0-rc.111; no behavior or dependencies changed.

Verification

• The package and lock root versions agree; behavioral implementation already passed 909 tests, distribution build, and architecture policy in PR Fix source publication authority across activity profiles #350.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Revert commit 59a8b3f before tagging; no runtime or persisted state changes.

Completion summary

The release identity is ready for protected-branch verification and exact candidate publication.

AGPL committer authorization

The base-owned workflow checks the provider-authenticated pull-request author against .github/approved-committers.json. There is no per-PR grant checkbox.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.