Skip to content

fix: address framework issues from first session#1

Merged
kraulerson merged 1 commit intomainfrom
fix/framework-session-feedback
Apr 6, 2026
Merged

fix: address framework issues from first session#1
kraulerson merged 1 commit intomainfrom
fix/framework-session-feedback

Conversation

@kraulerson
Copy link
Copy Markdown
Owner

Summary

  • Expand branch-safety.sh to catch gh repo create --push and gh pr merge bypassing branch protection
  • Add step-sequencing instruction to CLAUDE.md — don't infer completion from local state
  • Add remote repo + branch protection to Builder's Guide init checklist
  • Document Nuitka + VTK packaging hang and Python version compatibility in Desktop Platform Module

Test plan

  • Verify branch-safety.sh blocks gh repo create --push on protected branches
  • Verify lint/type-check pass on modified files

🤖 Generated with Claude Code

- branch-safety.sh: expand regex to catch `gh repo create --push`
  and `gh pr merge` in addition to `git push`
- CLAUDE.md: add step-sequencing instruction — follow numbered steps
  in order, don't infer completion from local state
- Builder's Guide: add "remote repo exists" and "branch protection
  configured" to Phase 2 init verification checklist
- Desktop Platform Module: add Section 3.4 documenting Nuitka +
  large native package hang and Python version compatibility chain

Includes regression test for branch-safety.sh pattern matching.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@kraulerson kraulerson force-pushed the fix/framework-session-feedback branch from 40a8125 to fd00ea4 Compare April 6, 2026 13:44
@kraulerson kraulerson merged commit a47cdbf into main Apr 6, 2026
1 of 5 checks passed
kraulerson pushed a commit that referenced this pull request Apr 6, 2026
Merge commits (e.g., "Merge pull request #1 from user/fix/branch")
contain branch names with "fix" in the message but have no file list
in git log --name-only output. The hook matched "fix" in the message,
found no test files (because merge commits list none), and flagged a
false positive.

Fix: skip commits whose message starts with "Merge " when scanning
for untested bug fixes.

Includes documentation of the root cause analysis in
docs/framework-feedback/stop-hook-test-detection.md.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
kraulerson pushed a commit that referenced this pull request Apr 6, 2026
Merge commits (e.g., "Merge pull request #1 from user/fix/branch")
contain branch names with "fix" in the message but have no file list
in git log --name-only output. The hook matched "fix" in the message,
found no test files (because merge commits list none), and flagged a
false positive.

Fix: skip commits whose message starts with "Merge " when scanning
for untested bug fixes. Includes regression tests verifying the
detection logic for both real fix commits and merge commits.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant