Skip to content

Repo Continuity v4.5.0

Latest
Latest

Choose a tag to compare

View all tags
@vector233 vector233 released this 07 Sep 02:49
v4.5.0
a137c2c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Repo Continuity v4.5.0

Repo Continuity now gives historical knowledge an explicit archival lifecycle. Daily work uses current knowledge and small open-task routes; historical evidence remains available without being read during ordinary discovery.

What Changed

  • Each open WORK or Initiative has its own Markdown route under zettelkasten/work/active/. Status, acceptance, checkpoints, and relationships remain authoritative at the original source path. Closure removes the route.
  • Archive long terminal WORK or Initiative records and retired knowledge notes into original-byte snapshots. Their stable source paths retain compact summaries, heading anchors, relationships, evidence links, and checksums. Preview, idempotent archive, and verified restore are available through the optional Companion Skill.
  • Archival checks unresolved acceptance, experience candidates, and gates. Open work and Initiatives with open children cannot be archived. Retiring a multi-file project Skill remains a deliberate directory-and-link update documented in the lifecycle.
  • Ordinary Doctor checks and status discovery exclude archive bodies and unrelated historical WORK records. A referenced terminal dependency is resolved from its summary; daily discovery stops before expanding older prerequisite chains. Use --full for complete route coverage, historical child membership, wiki links, and archive checksums.
  • Existing projects get an explicit, previewable routing migration. A newly copied route directory starts pending, so an empty upgrade directory cannot silently hide existing tasks.
  • This release also includes the post-v4.4.1 fixes for per-line required-heading detection and baseline error examples that track the actual Companion Skill default version.

The core remains Markdown and Git only. WORK IDs, canonical paths, the repo-continuity Skill ID, and the payload marker remain stable. Scripts remain optional and are not copied into the downstream core.

Upgrade Existing Projects

Install the v4.5.0 Companion Skill and follow the three-way upgrade guide on an isolated task branch, preserving the project's pre-upgrade checkpoint and local customization. After reconciling the new lifecycle and entry rules, build the open-work routes explicitly:

# SKILL_ROOT is the installed v4.5.0 Companion Skill directory.
# PROJECT_ROOT is the initialized project being upgraded.
python3 "$SKILL_ROOT/scripts/workflow_archive.py" reindex --root "$PROJECT_ROOT" --dry-run
python3 "$SKILL_ROOT/scripts/workflow_archive.py" reindex --root "$PROJECT_ROOT"
python3 "$SKILL_ROOT/scripts/workflow_doctor.py" --root "$PROJECT_ROOT" --full --strict

Review the preview before applying. Resolve invalid source metadata and coordinate the rebuild with other writers. The same routes can be created manually with Markdown; mark Routing status: ready only after every open record is represented. Existing helpers that relied on a full Doctor audit must now request --full explicitly. Advance the project's recorded template baseline only after review and validation pass.

Installation, upgrade, and reindex do not archive or delete project history automatically. Archive selected historical bodies only after preserving applicable knowledge and closure evidence. See the canonical lifecycle and archive/restore helper guide.

中文说明

此版本将归档纳入正式生命周期。日常任务通过轻量入口定位当前工作，已归档正文和无关历史任务退出默认扫描；原路径、结论、关系和可校验原文仍可追溯和恢复。

旧项目升级后需要显式建立任务入口。 按中文升级指南协调新规则，再预览并执行上面的 reindex，最后运行完整检查。升级不会自动归档或删除历史。已有自动化若需要检查全部历史，请明确使用 Doctor 的 --full 选项。

Assets 2
Loading