[K2A] Persist K1 Program history in SQLite #14
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/creatidy-kernel!14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-5-k2a-sqlite"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements Creatidy/creatidy-kernel#5 and keeps the issue open for owner integration.
Program.apply().fdinfo.mnt_idchecks bind the main DB, WAL/SHM/journal sidecars, and backup artifacts to the actual filesystem. Hidden/split/file-only mounts, OverlayFS, tmpfs/ramfs, volatile storage, network filesystems, and checkpoint-disabled F2FS are rejected.locking_mode=EXCLUSIVE, actual runtime/capability/pragma evidence, and a process/thread ownership guard. Online backups fsync files/directories around atomic publication; amendment inputs follow K1 canonical ordering.Validation for HEAD
f588de5bcc0d2e8f1b7ae50618cafd8dc7d6c25d:make checkpassed (142 tests, lint, basedpyright, import contract, secret scan, diff check);make package-checkpassed; Forgejo CI run #1937 is successful. An independent Local GPT-6 Astra max review returnedAPPROVEfor this exact HEAD with no blocking findings. The completed review ledger and optional nonblocking test suggestions are recorded on Issue #5. This PR is open, targetsdevelop, and has not been merged.kilo referenced this pull request2026-09-24 22:40:23 +00:00
kilo referenced this pull request2026-09-25 02:12:49 +00:00