v0.2.3: concise progress views

v0.2.3: concise progress views

Experimental prerelease, October 17, 2026.
Bundle: context-docs 0.2.3, adopt-context-docs 0.1.12 and unchanged
standard 0.1.1. Previous bundle: v0.2.2.

What changes

Both skills favor a concise progress overview: the documented goal, meaningful
outcomes, dependencies and blockers, and the next action. Link to canonical
evidence instead of repeating test counts, review rounds or release receipts.

• Keep decisions and rationale, approval boundaries, unresolved work and relevant
  qualifications visible where they affect a status or next action.
• Preserve existing views, formats, owner edits and record locations. The preference
  for concision does not authorize reshaping an established layout or deleting
  unique information. Adapt detail to the project and explicit requests.
• Use no fixed line limit or required template. Add no tracker, evidence store,
  web viewer or runtime dependency merely to shorten a view.

The packaged progress guide
owns this guidance. Adoption follows it when creating a supported view; core
maintains the same view during authorized everyday work. Default inline creation
already ships in v0.2.2; this release refines how much detail the overview carries.

Existing projects and upgrades

Installation and upgrades remain separate actions. Follow the
upgrade guide for both complete sibling packages,
preserving local customizations. Publication does not update installed skills.

Existing context paths, equivalent setup rules, adoption dates, owner decisions,
local-only storage boundaries, logging settings and saved studies stay in place.
An upgrade alone does not create or rewrite project views. Explicit visualization
requests can reshape an agreed view; ordinary maintenance preserves its format.
Audits remain read-only, and progress does not enable logging or background tracking.

Evidence and qualification

The focused copied-candidate smoke
runs one session per client, each with synthetic re-adoption and a separate
existing linked-table update. Both produce concise, source-linked progress and
preserve decisions, blockers and existing layouts. Codex resolves 10 relative
links; Claude resolves 12 plus one local anchor. The cases are guided and scored
by Sol, the change author; the two tasks share a session in each client.

Codex fails the strict write boundary. It creates and removes a fixed
/tmp/cedar-context-before.json hash snapshot outside the four permitted Markdown
files. Both operations succeed; the path is absent afterward. Its prior absence
or contents were not inventoried and remain unknown. The qualification and exact
outputs are retained without correction or retry. The protected repository,
installed packages and earlier study/evidence inventory passes separately;
that comparison does not establish preservation of the temporary path or global state.

The earlier artifact review
records Opus 5.5 review and one focused follow-up resolving a context-summary
authorization condition. It is separate from native behavior and retains its
original scope and final-wording qualifications.

These narrow cases do not establish general reliability, implicit discovery,
fresh setup, cross-session continuity, usability or user benefit. The full suite,
sparse/local-only, audit/repeat and explicit-extra-detail branches remain unrun.
All earlier studies and review records remain unchanged.

Preparation and publication status

The preparation record owns current local checks,
package identities, desktop/mobile previews and preservation. No new native
model trial or counterpart review is part of this release preparation.

Published as an experimental prerelease
on October 17, 2026, from 0c053d6ec37eaa57640d4330e11ae257c86a61a1, 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, concise-view guidance, the smoke
scope qualification, canonical visual/source maps and SEO titles without em dashes.

The publication record owns identities, 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
new browser rendering or user benefit.