Skip to content

myPKA scaffold v5.5.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Aug 10:50
v5.5.2
7b77800

myPKA scaffold v5.5.2

Housekeeping release: fixes in preparation for the next major version. Everything here makes what already shipped correct, findable, and checkable. If you run the Cockpit, rebuild the web bundle and re-run the regen after updating (one field was renamed; your existing notes keep working).

Changed

  • tom_context is renamed to user_context across the Cockpit's Outer World annotation schema: note frontmatter, the mirror column, the regen, the server payload, the web client, the template, and the example notes. The old key keeps working: the regen reads tom_context as a deprecated alias of user_context (read old, write new), so existing notes need no edits, and the news migration script renames the key when it carries a note over. New notes should use user_context. Details in the Cockpit changelog (1.6.0) and sqlite-extension/DATA-CONTRACT.md section 14.

Fixed

  • The eight seeded PKM samples now carry the YAML frontmatter they claim to demonstrate. They shipped in the retired inline-field format while presenting themselves as the canonical shape, so copying a sample produced a non-compliant note and the Cockpit Properties tab rendered empty. Every sample is regenerated from its template in Team Knowledge/Templates/; the narrative content is unchanged.
  • Three shipped subsystems are reachable from the navigation hubs again. The task lifecycle (Team Knowledge/tasks/ and its SOPs), Weekly Reports, and the Templates plus scripts layer were absent from Team Knowledge/INDEX.md, PKM/INDEX.md, and the root folder map. The missing SOP rows and script sections are wired in.
  • Broken wikilinks repaired and stale strings corrected. The genuinely dead links (10 of 687) and the ambiguous bare AGENTS links now resolve with path-suffix targets; a dead anchor, a retired product name, and an outdated Cockpit version row are corrected.
  • Engineering comments no longer reference internal process residue. A comment sweep replaces internal names and private-vault paths with role wording and shipped-path references, the same policy the 5.5.1 privacy fix applied to authorship.

Added

  • validation-script.sh learns --links, --indexes, and --all. The baseline structural check is unchanged; the new opt-in groups verify wikilink resolution over every markdown file and INDEX coverage (SOPs, Workstreams, Guidelines, Templates), so the two defect classes fixed above cannot recur silently. Run bash validation-script.sh --all . from the folder root.

Security

  • The repository's git history was re-initialized to a clean root. A privacy hardening pass removed all pre-5.5.1 history from the public repository; published release artifacts are unchanged, and v5.5.1 remains byte-identical to its released ZIP. If you cloned before 2026-08, re-clone or hard-reset your clone; the full maintenance notice lives in README.md.
  • A required privacy gate now guards the repository. Every push and pull request runs scripts/check-no-personal-data.py --require-config over the full checkout as a required status check on main, so the class of leak fixed in 5.5.1 cannot land again unnoticed.

Download

  • Latest (stable URL): mypka-scaffold-latest.zip — always resolves to the newest scaffold.
  • This version (pinned): the mypka-scaffold-v5.5.2.zip asset attached below.

Unzip it into a folder, open that folder in your LLM tool, and paste initialize yourself in this folder — see the README for the full setup.

Integrity

  • ZIP sha256: efd74e6eda814a50a071d04f438fe8776eb02817c132d434d17b3aaee9d83348

Full changelog: CHANGELOG.md

Assets 5
Loading