alphazede/bearing-lite
v1.1.8Apache-2.0
Skills-first portable plugin that routes repository work through the smallest valid planning stages and agent roles, using project Markdown as the only task record.
Changelog
[Unreleased]
1.1.8 - 2026-10-13
Fixed
- Fixed Codex registering none of Bearing Lite's hooks when installed from the repository, which left sessions without activation advice or the write-set lock: Codex 0.162.1 silently drops plugin hooks when the root
plugin.jsoncarries$schema. Install Codex from the local marketplace thattools/prepare-codex-plugin.mjsprepares, which holds the same package bytes with only that key omitted; the portableplugin.jsonis unchanged. #188 - Fixed session-start activation reporting
write_lock: absenteven though the shippedhooks/hooks.jsonregisters the write-set lock; detection now reads command-form registrations as well asargs. #188 - Fixed Codex
apply_patchedits bypassing the write-set lock and Test Engineering routing, because the patch body arrives intool_input.command, which neither adapter read. Patches to protected planning files are now denied, and patches that add or change test files reach Test Engineering. Shell commands are unaffected. #188 - Fixed CI and the publish workflow passing with no Codex hooks registered. A required native gate now runs
node --test test/native/codex-hook-discovery.test.mjsagainst pinned Codex CLI 0.162.1 and checks that every hook and skill registers. Hook component tests no longer inherit a parent session'sBEARING_ROLE. #188
1.1.7 - 2026-10-13
Changed
- Added draft requirement-register prechecks before specialist dispatch, catching mechanical errors without spending semantic correction rounds. #178
- Constrained planning corrections to named changes and required exact-text closure evidence. #180
- Standardized packaged skills on a 650-word limit while retaining the existing line limit. #179
- Updated pinned CI and publishing actions. #181
- Required shared-machine test isolation, five consecutive engine-starting runs, concurrent qualification, and explicit resource and gate-time declarations; kept schema metadata optional for existing plans. #184
- Aligned all seven package and host manifests to 1.1.7 and reconciled the accumulated release record (#187).
Fixed
- Rejected incomplete or malformed planning manifests that previously passed the planning-freeze projection gate. #177
- Required prompts to map acceptance criteria to observable evidence and name trust boundaries with negative checks. #183
- Fix
tools/render-dod-manifest.mjsexiting 0 without output when invoked through a symlinked install path; symlinked directory and file invocations now behave identically to the real path (#185).