v0.2.6: filter metadata and keep references portable

v0.2.6: filter metadata and keep references portable

Experimental prerelease, October 19, 2026.
Bundle: context-docs 0.2.6, adopt-context-docs 0.1.15 and unchanged
standard 0.1.1. Previous bundle: v0.2.5.

What changes

Both skills strengthen information selection before saving context or an enabled
journal event:

• Omit incidental usernames, account identifiers, private evidence locations and
  personal installation state from shared additions. Summarize useful findings
  instead of copying raw tool output.
• Prefer repository-relative project references. For private evidence, use a
  suitable public summary, stable ID or hash with access limits; an identifier
  does not make the underlying evidence inspectable by other readers.
• Keep meaningful outcomes and their qualifications in a canonical location,
  linking from summaries instead of repeating routine bookkeeping.
• Preserve decisions, rationale, conditions, uncertainty, blockers and supporting
  evidence. Useful local paths and necessary diagnostic relationships still
  belong in appropriate destinations; filtering does not mean removing all
  environment detail.

The core guidance
owns the rule; adoption applies it through the sibling skill. The
guide explains the sharing
boundary. No automatic redaction, secret scanner or historical cleanup is added.
An enabled journal can be tracked/shared; enabling logging does not make it private.

Evidence and qualifications

The candidate smoke
runs one fresh Codex and one Claude Code session, each with copied skills and two
fictional cases: public re-adoption and personal offline maintenance. Both pass
the visible saved-Markdown filtering, relative-link, content-quality and edit-scope
checks. Useful personal paths, decisions, evidence limits and owner text survive.

Claude could not locate an unlinked private operator note with its restricted
discovery tools. Filtering incoming metadata from that note remains untested in
Claude. Its output removes metadata already present in context and accurately
reports the missing source. This fixture coverage gap remains attached to the
original outputs, without a session rerun or output repair.

These are guided, Sol-authored and Sol-scored cases with explicit candidate paths.
They do not establish installed behavior, implicit loading, automatic everyday
application or general privacy guarantees. Native journal capture was not tested;
logging is off in the fixtures. The separate
offline controls cover six authored
examples, including journal schema/helper use, and retain the qualified Opus
artifact review and final schema correction checked locally. They are not a
general semantic grader or evidence of automatic filtering.

Existing projects and upgrades

Publication and installation are separate actions. Preserve local customizations
and install both complete sibling packages using the upgrade guide.
Installed v0.2.5 keeps its existing guidance until separately upgraded.

Keep existing context paths, layouts, setup/collaboration rules, owner decisions,
adoption dates, local-only boundaries, logging settings and saved studies.
No storage migration, background process or runtime change is required. This
release does not authorize moving records, rewriting frozen evidence or sanitizing
older Git history. Audits remain read-only.

Preparation status

The preparation record retains its original unpublished
scope, local checks, package/build identities and preservation separately from
the unchanged native smoke. Publication changes release labels; the skill
packages and original evidence remain unchanged. No new model trial or counterpart
review is part of publication. Installed upgrades remain a separate action.