Skip to content

LogicMargin v0.9.14

Choose a tag to compare

@github-actions github-actions released this 10 Nov 07:33
· 29 commits to main since this release

LogicMargin 0.9.14

Replaces the bundled examples with original fictional subscription and task-pipeline workflows. Their evidence now refers only to authored rules in this repository, with verified file and excerpt digests. New review identities keep the fictional examples separate from existing local reviews, comments, drafts and sessions; existing user data is preserved.

Public source guides, layout prototypes, test fixtures and development instructions no longer carry the previous examples' internal project details, machine paths or live service links. Existing screenshots already use a fictional checkout example. The native programs and DSH bundle are rebuilt together so the pinned launcher uses this version's cleaned UI.

This change covers the current source tree and these newly built packages. It does not erase older Git history, tags, Releases, downloaded packages or copies. Review and back up existing data before changing any installed service; this release does not migrate or delete review content.

DSH compatibility remains pinned to 0.2.2-rc.1. Download and verify this Release's tgz before installing it into the intended profile. npm distribution and community/Discover listing are separate from GitHub Release publication. The webpage updater still targets Codex; DSH package updates use its host installer.

Windows startup now treats access-denied during lock-directory churn as bounded contention. It retains the existing deadline, cancellation and ownership checks, and reports the original error when probing cannot succeed. Windows CI repeats the directory competition regression 25 times. The v0.9.10 tag is preserved without a public Release because its native Windows gate reproduced this failure.

Windows update status reads and atomic status replacement now retry brief sharing conflicts with a 250 ms retry budget while retaining the original error on persistent failure. Complete temporary writes, Sync, Close and Rename remain in place. Update tests flush their shutdown response before closing the fixture server. Prewarm scheduling and cache checks are separated from heavy fallback layout execution; production computation budgets and worker counts are unchanged. The v0.9.11 tag is preserved without a public Release after its native gates found these issues.

Windows now rolls back a lock claim when publishing its directory succeeds but acquisition confirmation fails. Cleanup checks the original directory identity and owner UUID, preserves unknown content, and reports persistent sharing failures. The original native race reproduced an orphan claim before this fix; both the competing recovery case and the full daemon package subsequently passed five repetitions under Windows race. The v0.9.12 tag remains unchanged without a public Release.

The Node compatibility service now retries Windows mkdir EPERM within the existing lock wait period. Persistent failure retains the original error, and zero-wait data locks still fail immediately. The retry does not inspect or remove another owner. Native Windows repeated concurrent startup and crash recovery 25 times and the full Node suite five times successfully. The failed v0.9.13 tag remains without a public Release.

Dense full-source correctness is checked with the existing syntax-test deadline. Engine checks retain the production deadline and accept only an explicit budget fallback with intact saved-source digests, no structural marks, and cache reuse; the ordinary diff limits and runtime budgets are unchanged.


  • 默认与复杂样例改为本仓库原创的虚构演示,明确标注合成规则来源;证据行号、片段摘要与文件指纹同步校验。
  • 新演示使用独立评审 ID,不把旧批注、草稿或历史并入无关内容,也不删除已有本地数据或真实会话。
  • 清理当前公开说明、布局原型及派生测试材料中的内部工程信息、本机路径和真实服务链接。五平台原生程序和 DSH 包统一重建,不再由新包启动旧版 UI。
  • 本次不撤回旧 Git 历史、标签、Release 或已下载副本,也不修改本机正式安装和评审数据。
  • DSH 兼容基线保持 0.2.2-rc.1;npm 发布和社区目录/Discover 收录分别核对,不把制品上传当作市场已收录。

Windows 锁目录竞争中的拒绝访问按既有期限重试;永久拒绝仍保留原错误,不删除未知锁、不放宽单写入者检查。v0.9.10 因原生门禁复现该错误未公开 Release,标签保留。

Windows 更新状态读写对短暂共享冲突采用 250ms 重试预算,持续失败保留原错误,仍采用完整临时写入、同步、关闭与原子替换。测试服务先刷出停机响应;预热并发与缓存断言使用独立检查,不放宽生产计算预算。v0.9.11 因门禁失败未公开 Release,标签保留。

Windows 获取服务锁失败时会核验目录身份和 owner UUID,并回收已经发布的本次 claim,避免活 PID 遗留锁持续阻止启动;他人锁和未知文件保留,持续共享占用仍明确报错。原生 Windows 已复现旧故障,修复后竞争用例与完整 daemon 包分别连续五轮 race 通过。v0.9.12 因门禁失败未公开 Release,标签保留。

Node 兼容服务的锁目录创建遇到 Windows EPERM 时,在原等待期限内重试;持续失败保留原错,零等待数据锁仍立即失败,重试不删除或接管其他 owner。原生 Windows 并发启动与崩溃恢复连续 25 次通过,完整 Node 测试连续五轮通过。v0.9.13 因门禁失败未公开 Release,标签保留。

密集全文的语法覆盖使用既有测试期限单独校验;引擎仍遵守生产预算,回退必须明确为 budget、保留原片段摘要、不带结构标记且可复用缓存。未放宽普通 diff 限制或运行时预算。