v0.2.5: coordinate shared context edits (experimental)

v0.2.5: coordinate shared context edits

Experimental prerelease, October 18, 2026.
Bundle: context-docs 0.2.5, adopt-context-docs 0.1.14 and unchanged
standard 0.1.1. Previous bundle: v0.2.4.

What changes

Both skills add a conditional rule for agents or sessions working concurrently
on the same context file:

• Agree on one writer per shared file before concurrent edits begin. Other
  participants return findings to that writer.
• Change writers through an explicit handoff, including when Codex and Claude
  share a checkout.
• Prefer narrow edits. After an edit conflict or stale-text failure, reread the
  current file and reconcile contributors' changes before retrying. Preserve
  newer work instead of replacing it from an old snapshot.

The core skill
owns the rule; adoption follows it.
The user guide
explains the shared-checkout workflow. Installing the skill in both clients does
not coordinate their sessions. This is guidance without file locking, automatic
merging or a guarantee against lost updates.

Evidence and qualifications

The candidate smoke
runs one native Codex session requesting Sol 6.1 and one Claude Code session
reporting Opus 5.5. Each uses copied candidate skills and two tiny fictional cases:
a peer-owned context and a context explicitly handed over to the acting session.
The prompt deliberately requires one stale queued replacement to exercise recovery.

Both leave the peer-owned context unchanged and return findings for its writer.
Both recognize the handoff, reread after the forced stale edit fails, and preserve
the newer schema result, decisions, owner text, blockers and evidence. Only the
permitted Progress and Next action sections change; all seven final context links
resolve per client.

Claude retries its own second text mismatch without another reread. This is
a procedural failure despite preserved final Markdown. The original tool ordering,
errors and outputs remain intact; the result is not an unqualified pass.

Codex's first read-only self-check rejects a valid anchor because it compares
heading capitalization incorrectly. A corrected check succeeds in the same
session; the assessor separately verifies links and section preservation.
Codex's responding model identity remains unconfirmed. The requested model is
recorded, and the original checking error is retained.

These are guided, Sol-authored and Sol-scored cases with explicit copied-skill
paths. The peer and handoff are simulated, not live simultaneous writers. They
do not establish installed behavior, implicit loading, automatic everyday
compliance, cross-session continuity, conflict frequency or general conflict
prevention. No output repair or model rerun occurred. The earlier offline
mechanism diagnostic and all earlier studies remain unchanged.

Existing projects and upgrades

Publication and installation are separate actions. Follow the
upgrade guide, preserving local customizations
and keeping both complete sibling packages. Installed v0.2.4 retains its earlier
guidance until separately upgraded; publication alone changes no installation
or project setup.

Preserve existing context paths, equivalent maintenance and collaboration rules,
adoption dates, owner decisions, layouts, local-only boundaries, logging settings
and saved studies. The change adds no runtime, background writer, lock service
or storage format. Audits remain read-only.

Preparation and publication status

The preparation record retains its original October 17
draft scope, local checks, package identities, website previews and preservation
separately from the earlier native smoke and artifact review. No new native model
trial or counterpart review is part of publication. Release labels change for
publication; the skill packages, original evidence and qualifications stay intact.
Installed upgrades remain a separately authorized action.