nsaspy/hackmode
1
0
Fork 0
Code Issues 46 Pull requests 55 Projects Releases Packages Wiki Activity Actions

Database: persist durable capture replay checkpoints #100

Closed
nsaspy wants to merge 5 commits from hackmode-rage-database/26-capture-checkpoint-20260830-1600 into master
pull from: hackmode-rage-database/26-capture-checkpoint-20260830-1600
merge into: nsaspy:master
Conversation 0 Commits 5 Files changed 5 +165 -4
nsaspy commented 2026-09-04 20:37:09 +00:00
Owner
Copy link

Issue #26 database-owned replay prerequisite.

RED-first acceptance at head 2b8dc9164879a38b54c3b13b4a50116cac2fbf40:

  • capture checkpoints are typed execution-graph records scoped by operation + capture session + source;
  • identical checkpoint construction preserves stable identity;
  • canonical persistence replay is idempotent;
  • latest checkpoint resolves deterministically to the greatest durable offset for one source;
  • source isolation is enforced;
  • negative offsets and invalid framing versions fail closed.

RED evidence: common-lisp-core failed on the intentionally missing checkpoint API while monorepo/boundary passed.

GREEN exact head 82b0a7ee38b89219cf241804ad1c809f9f18462e: core, monorepo, and agent-framework-boundary all pass.

Implementation remains under the canonical Hackmode/Tek9 execution-graph boundary. No parser actor, proxy, Hackpert reasoning, StarIntel product work, second database, or shadow graph is included.

Issue #26 database-owned replay prerequisite. RED-first acceptance at head `2b8dc9164879a38b54c3b13b4a50116cac2fbf40`: - capture checkpoints are typed execution-graph records scoped by operation + capture session + source; - identical checkpoint construction preserves stable identity; - canonical persistence replay is idempotent; - latest checkpoint resolves deterministically to the greatest durable offset for one source; - source isolation is enforced; - negative offsets and invalid framing versions fail closed. RED evidence: `common-lisp-core` failed on the intentionally missing checkpoint API while monorepo/boundary passed. GREEN exact head `82b0a7ee38b89219cf241804ad1c809f9f18462e`: core, monorepo, and agent-framework-boundary all pass. Implementation remains under the canonical Hackmode/Tek9 execution-graph boundary. No parser actor, proxy, Hackpert reasoning, StarIntel product work, second database, or shadow graph is included.
feat(database): export capture checkpoint boundary
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 1s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 3s
Details
core / common-lisp-core (pull_request) Failing after 47s
Details
monorepo / hygiene (pull_request) Successful in 4m13s
Details
82b0a7ee38
nsaspy closed this pull request 2026-09-04 20:53:31 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 1s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 3s
Details
core / common-lisp-core (pull_request) Failing after 47s
Details
monorepo / hygiene (pull_request) Successful in 4m13s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
feature
New feature or capability

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
refactor
Code cleanup without behavior change

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
invalid
question
refactor
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/hackmode!100
No description provided.