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

Hackpert: expose loop strategy transition inspection #158

Open
nsaspy wants to merge 6 commits from hackmode-rage-hackpert/29-loop-transition-inspection into master
pull from: hackmode-rage-hackpert/29-loop-transition-inspection
merge into: nsaspy:master
Conversation 0 Commits 6 Files changed 4 +241 -2
nsaspy commented 2026-09-04 20:58:42 +00:00
Owner
Copy link

Slice

#29 / #27 Hackpert-owned operator inspection: expose one bounded, side-effect-free transition record for symbolic/direct loop decisions so LISH/UI consumers can explain symbolic -> direct -> symbolic without inferring it from mutable controller state.

RED contract

The regression requires operation/run scope, decision kind/reason, previous/next reasoning strategy, and previous/next non-progress counts. It also requires defensive string copies and fail-closed rejection when the before/after scope or decision/next-state strategy disagree.

This draft intentionally wires the regression before implementation.

Boundary

Inspection only. No provider execution, canonical mutation, persistence/database internals, model executor, second scheduler, raw Prolog execution, or StarIntel product work.

## Slice #29 / #27 Hackpert-owned operator inspection: expose one bounded, side-effect-free transition record for symbolic/direct loop decisions so LISH/UI consumers can explain `symbolic -> direct -> symbolic` without inferring it from mutable controller state. ## RED contract The regression requires operation/run scope, decision kind/reason, previous/next reasoning strategy, and previous/next non-progress counts. It also requires defensive string copies and fail-closed rejection when the before/after scope or decision/next-state strategy disagree. This draft intentionally wires the regression before implementation. ## Boundary Inspection only. No provider execution, canonical mutation, persistence/database internals, model executor, second scheduler, raw Prolog execution, or StarIntel product work.
tests: use repository-native condition checks
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 4s
Details
core / common-lisp-core (pull_request) Failing after 33s
Details
monorepo / hygiene (pull_request) Successful in 5m48s
Details
93c1a3d060
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 4s
Details
core / common-lisp-core (pull_request) Failing after 33s
Details
monorepo / hygiene (pull_request) Successful in 5m48s
Details
This pull request has changes conflicting with the target branch.
  • source/hackmode-core/expert/transition-inspection.lisp
  • source/hackmode-core/hackmode-tests.asd
  • source/hackmode-core/hackmode.asd
  • source/hackmode-core/tests/expert-transition-inspection.lisp
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin hackmode-rage-hackpert/29-loop-transition-inspection:hackmode-rage-hackpert/29-loop-transition-inspection
git switch hackmode-rage-hackpert/29-loop-transition-inspection

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff hackmode-rage-hackpert/29-loop-transition-inspection
git switch hackmode-rage-hackpert/29-loop-transition-inspection
git rebase master
git switch master
git merge --ff-only hackmode-rage-hackpert/29-loop-transition-inspection
git switch hackmode-rage-hackpert/29-loop-transition-inspection
git rebase master
git switch master
git merge --no-ff hackmode-rage-hackpert/29-loop-transition-inspection
git switch master
git merge --squash hackmode-rage-hackpert/29-loop-transition-inspection
git switch master
git merge --ff-only hackmode-rage-hackpert/29-loop-transition-inspection
git switch master
git merge hackmode-rage-hackpert/29-loop-transition-inspection
git push origin master
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!158
No description provided.