v0.1.8: local-only context and opt-in auto logging (experimental)

v0.1.8: experimental prerelease

Bundles context-docs 0.1.8, adopt-context-docs 0.1.9 and standard 0.1.1.
Experimental prerelease, published October 10, 2026 from 8bda86ce8e23d14874dcb22e0af7b2e581717ee7.
Release-commit static checks
and landing-page checks passed.

Changes since v0.1.6

Both skills now support explicitly requested local-only context, excluded from Git.
They check Git tracking separately from effective ignore rules, read named ignored
entry points directly, and keep local content out of shared documents. Existing
tracked context is preserved until migration scope is agreed. The directory and
instruction locations follow the project's existing setup.

The opted-in auto logging preference now also covers explicitly selected
local-only context inside Git. With no project logging setting, the read-only
policy helper requires all chosen context paths and the journal directory to be
untracked and effectively ignored. It checks exposed descendants and prospective
journal files; missing scope, negated exclusions, tracked targets, aliases,
symlinks, nested repositories or detection errors leave logging unchanged.
Every explicit logging setting, including off, takes precedence. Shared Git
context and confirmed no-Git behavior retain their existing defaults.

An enabled local journal can retain significant events when current context has
no Git history. It does not save complete document versions; snapshots or backups
serve that separate need. The writer, schema and standard are unchanged.

The website guide adds the canonical local-only setup and auto-logging prompts.
Page and Open Graph SEO titles use no em dashes. The build still publishes only
its explicit public file allowlist.

Installation and upgrade

Follow the user guide. Update complete sibling
skill folders together, preserving local customizations. Adoption requires the
sibling core package. Existing projects keep their maintenance rules, original
adoption dates, context paths, ignore rules, logging settings and event history.
Installation and upgrades do not select local-only storage or enable logging.
A previously selected auto preference can add a logging setting during later
authorized setup or maintenance when an unset local-only project newly qualifies.
Audits remain read-only. Ordinary Markdown maintenance needs no runtime;
optional journal and policy helpers require Python 3.9+, and policy detection
requires Git.

Validation and limits

The auto-policy validation record
records 156 passing mechanical tests, static and package checks, the website
build, and six bounded native Claude Code/Codex sessions. Four native sessions
preceded review fixes; the two final-package sessions checked fresh setup in nine
projects per client, including a tracked case alias and a prospective journal suffix exception.
Repeat/no-change maintenance and audit evidence belongs to the earlier candidate.
All seven published final-native file identities match this release candidate;
the release validation record records all 15 packaged
file hashes and the successful candidate GitHub Actions runs.

Claude Opus 5.5 drafted the helper/tests; Codex integrated review fixes and ran
checks. Initial failures and review qualifications
are retained in the auto-policy validation record. The release-note review is
recorded separately. The seven broader
local-only agent scenarios
remain unexecuted. Historical studies and existing setups are preserved.

These constrained, authored checks do not establish privacy guarantees, implicit
skill selection, automatic instruction loading, general reliability, JSONL
necessity or user-effort savings. Known new paths still need explicit checks:
prospective probes cannot predict every future negated target. Absent Unicode
normalization aliases are not exhaustively tested, and large directory walks
remain unbounded. See the changelog and
earlier evidence for retained failures and limitations.