Extract role communication style into three automatic packages with schema-3 treatment: "communication_context" metadata. Forks preserve this declaration; the owner can reject conflicting ablation assignments without disabling unrelated skills.
Before: the new communication-package test failed because the packages did not exist.
After: python3 -m unittest discover -s tests -v passed all 19 checks at the exact source head above, including package and redistribution/archive checks.
Documentation disposition
updated — README describes treatment metadata and the owner boundary.
Ablation decision
required — existing communication-context contrast; explicit metadata approved by the Operator on 2026-11-14. No study is run.
Merge Danger
Door: two-way for future assignment; published release bytes remain immutable.
Blast Radius: package validation, role communication defaults and authoring guidance. Revert the integration pin/assignment to roll back future use; retain the release for captured sessions.
Reviewer prerequisites
Python 3; no credentials, provider or paid calls.
Manual Test Plan
Automated checks establish package contents and archive integrity; Operator review assesses the extracted prose. They do not establish model effectiveness.
python3 -m unittest discover -s tests -v
Expected: 19 passing checks. Stop on a failure; retain its output and correct source in a new release rather than changing the published tag.
Post-Merge Cleanup
Leave v0.11.0 intact and keep the branch/worktree until coordinated product review finishes.
## Summary
Extract role communication style into three automatic packages with schema-3 `treatment: "communication_context"` metadata. Forks preserve this declaration; the owner can reject conflicting ablation assignments without disabling unrelated skills.
```text
role package → proportional answers + Markdown + acknowledgement style
owner → publication identity/order + complete artifacts + authority
```
Immutable release: v0.11.0, source dd7b9c9d0b07707a53e1ed813a075d002db555d6. Existing releases remain unchanged. Product integration: RelayView issue 1031.
## Evidence
Before: the new communication-package test failed because the packages did not exist.
After: `python3 -m unittest discover -s tests -v` passed all 19 checks at the exact source head above, including package and redistribution/archive checks.
## Documentation disposition
updated — README describes treatment metadata and the owner boundary.
## Ablation decision
required — existing communication-context contrast; explicit metadata approved by the Operator on 2026-11-14. No study is run.
## Merge Danger
**Door:** two-way for future assignment; published release bytes remain immutable.
**Blast Radius:** package validation, role communication defaults and authoring guidance. Revert the integration pin/assignment to roll back future use; retain the release for captured sessions.
## Reviewer prerequisites
Python 3; no credentials, provider or paid calls.
## Manual Test Plan
Automated checks establish package contents and archive integrity; Operator review assesses the extracted prose. They do not establish model effectiveness.
```sh
python3 -m unittest discover -s tests -v
```
Expected: 19 passing checks. Stop on a failure; retain its output and correct source in a new release rather than changing the published tag.
## Post-Merge Cleanup
Leave v0.11.0 intact and keep the branch/worktree until coordinated product review finishes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Extract role communication style into three automatic packages with schema-3
treatment: "communication_context"metadata. Forks preserve this declaration; the owner can reject conflicting ablation assignments without disabling unrelated skills.Immutable release: v0.11.0, source
dd7b9c9d0b. Existing releases remain unchanged. Product integration: RelayView issue 1031.Evidence
Before: the new communication-package test failed because the packages did not exist.
After:
python3 -m unittest discover -s tests -vpassed all 19 checks at the exact source head above, including package and redistribution/archive checks.Documentation disposition
updated — README describes treatment metadata and the owner boundary.
Ablation decision
required — existing communication-context contrast; explicit metadata approved by the Operator on 2026-11-14. No study is run.
Merge Danger
Door: two-way for future assignment; published release bytes remain immutable.
Blast Radius: package validation, role communication defaults and authoring guidance. Revert the integration pin/assignment to roll back future use; retain the release for captured sessions.
Reviewer prerequisites
Python 3; no credentials, provider or paid calls.
Manual Test Plan
Automated checks establish package contents and archive integrity; Operator review assesses the extracted prose. They do not establish model effectiveness.
Expected: 19 passing checks. Stop on a failure; retain its output and correct source in a new release rather than changing the published tag.
Post-Merge Cleanup
Leave v0.11.0 intact and keep the branch/worktree until coordinated product review finishes.