v0.2.0: Markdown progress views (experimental)

v0.2.0: Markdown progress views

Experimental prerelease, October 16, 2026.
Bundle: context-docs 0.2.0, adopt-context-docs 0.1.10 and unchanged
standard 0.1.1. GitHub prerelease.
Previous bundle: v0.1.9.

What changes

Ask Context Docs to visualize progress in Markdown. It guides the agent to show
the documented goal and completion conditions, completed/active/blocked/proposed
work, meaningful advances, dependencies and the next action, with source links.
Use an existing context section or a linked Markdown file that fits the project.
An existing view is refreshed during authorized context maintenance.

The guidance distinguishes activity, useful learning and completed outcomes.
Relevant Git history, retained dated notes or an existing optional journal can
support a possible stall, not definitive loop detection. Missing history
leaves repetition unknown. No completion percentage or live agent activity is
invented. Markdown stays authoritative; no web viewer, service or extra runtime
dependency is added. See the guide
and synthetic example.

Adoption routes to the core progress guide while preserving existing layouts and
equivalent setup rules. The website update adds a progress section and the same
canonical prompt to the landing page and beginner guide. It retains explicit
experimental/released labels, SEO titles without em dashes and the nine-file
public build boundary.

Upgrade and preservation

Follow the upgrade guide, reviewing complete
sibling packages and preserving local customizations. No project re-adoption,
new tracker or document migration is required. Existing maintenance rules,
adoption dates, context paths, ignore rules, logging settings and saved history
remain in place. Audits stay read-only; reading relevant retained history does
not enable logging or change an explicit off setting.

Publishing this release does not update installed skills or existing project
setups. A new view is written on request; existing views can be maintained through
the loaded project rule. Installing the packages alone does not prove that a client
loads the rule or automatically selects the skill.

Evidence and known limits

• The artifact review retains one initial
  Opus 5.5 review and Sol's verified dispositions. The revised instructions did
  not receive a second model review.
• The focused smoke check ran
  two fresh, guided Claude Code sessions on one synthetic fixture: create a linked
  view, then refresh it from a newer retained result. The copied development skill
  was read explicitly. Goal/status, proposal/history distinctions and write
  boundaries passed; all 37 checked link occurrences resolved.
• Known presentation gap: two advances bullets in the smoke outputs lack
  their own inline source links, although their facts are linked elsewhere in the
  view. The exact outputs and this partial result remain unchanged.
• The full seven-scenario suite has not run. The smoke did not test native Codex,
  adoption, local-only progress, read-only audit, no-change repeat, Git/journal
  history or default automatic loading. It establishes no general reliability,
  privacy, stall-detection accuracy or target-user usability benefit.

Earlier feature checks passed 18 packaging/static regression tests, 12 site tests
and both skill validators. These are separate from the two native smoke sessions.
The release-preparation record records current website
tests/build, package identities and preservation checks. Historical studies,
reviews, failed observations and previous release records are preserved.

Publication status

Published as an experimental prerelease
on October 16, 2026, at d341695fd278cc31b17bae0154b459574ebf4444, after its
static checks
and website checks
passed. Deployment
passed from the same commit. All eight checked public responses match the build;
both pages show the progress section, experimental/released status and SEO titles
without em dashes. The publication record retains
response hashes, the initial urllib HTTP 403 observation and successful ordinary
curl checks. These checks do not establish crawler access or indexing.

Packages match the preparation identities. Existing setups, installed skills,
saved studies and prior evidence are preserved. No installed upgrade or new native
model trial is part of publication.