v0.2.4: clarity without losing meaning

v0.2.4: clarity without losing meaning

Experimental prerelease, October 17, 2026.
Bundle: context-docs 0.2.4, adopt-context-docs 0.1.13 and unchanged
standard 0.1.1. Previous bundle: v0.2.3.

What changes

Both skills prefer clear, direct sentences and consistent project terminology
within authorized context edits. Split crowded sentences while preserving
conditions, uncertainty, rationale and evidence.

• Keep conditions attached to their actions: a passing check can permit asking
  for approval without granting that approval.
• Keep unknowns accurate: missing evidence is not a failed result, and an
  unrecorded actor remains unknown.
• Preserve decisions, their reasons and source links. Clearer wording must not
  strengthen the evidence or turn a proposal into an approved decision.
• Preserve existing layouts and unrelated owner text. The preference does not
  authorize broad copyediting or require ASD-STE100 compliance, a controlled
  dictionary, sentence limits or a new template.

The core skill
owns the preference; adoption follows it
within its existing scope. Concise Markdown progress and everyday maintenance
continue as before; no new invocation is required for the writing preference.

Existing projects and upgrades

Installing or upgrading remains a separate action. Follow the
upgrade guide, keeping both complete sibling
packages and preserving local customizations. Publication does not upgrade
installed skills or rewrite project setups.

Existing context paths, equivalent rules, adoption dates, owner decisions, layouts,
local-only boundaries, logging settings and saved studies stay in place.
Audits remain read-only. The preference adds no runtime, background tracking or
new storage format.

Evidence and qualification

The copied-candidate smoke
runs one fresh native Codex session requesting Sol 6.1 and one Claude Code session
reporting Opus 5.5. Each performs two tiny synthetic tasks: re-adoption and
maintenance of crowded prose. Both preserve the conditions, unknowns, rationale
and evidence, with all eight local context links resolving per client. Only the
permitted sections of two context files change in each fixture.

Claude's final chat report adds an unsupported gendered pronoun for Noor.
The saved Markdown uses Noor's name and retains the correct approval condition.
The original report and qualification are retained without correction or retry.
Codex's responding model identity remains unconfirmed; the requested model is recorded.

These are guided, Sol-authored and Sol-scored writing cases with explicit candidate
paths. They do not establish implicit loading, automatic everyday application,
fresh setup, cross-session continuity, general reliability or user benefit.
An earlier tiny text comparison scored 12/12 for both original and rewritten
notes; no comprehension gain was demonstrated. Human reading effort and
ASD-STE100 compliance were not measured. Earlier smoke and review evidence,
including the v0.2.3 scope failure, stays unchanged.

Preparation and publication status

The preparation record records current local checks,
package identities, website previews and preservation separately from the earlier
native smoke and artifact review. This preparation performs no new model trial
or counterpart review. The preparation record retains its original draft/unreleased scope and earlier
package, preview and preservation checks. Publication uses released labels while
keeping the same skill packages and smoke qualification.

Published as an experimental prerelease
on October 17, 2026, from 73b15acbe570bacba9bcb43d24ccbba141d3bb4b, after
static checks
and the website build passed.
Deployment passed
from the same revision. All eight checked live public resources return HTTP 200
and match that build, including released labels, clarity guidance, the smoke
qualification and SEO titles without em dashes.

The publication record owns release/deployment identities,
artifact and response hashes, and verification limits separately from the unchanged
preparation record. Installed skills, setup rules, saved
studies and original smoke/review evidence are preserved. No new native trial,
counterpart review or installed upgrade is part of publication. Live checks verify
response bytes and HTML metadata, not browser rendering, indexing or user benefit.