fix: stop shipping dev-session .claude/ artifacts in the source tree #45
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/45/head"
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?
Summary
A source clone carried maintainer-session Claude Code artifacts:
.claude/commands/madtea-dev.md(the contributor checklist pointer — canonical content lives in docs/contributing/adding-commands.md) and two hookify*.local.mdrules. These are dev-session tooling for THIS checkout, not product: project-scoped.claude/files only load for sessions inside a madtea clone, so they do nothing for madtea users elsewhere — and where they would load, they impose maintainer-only workflow on contributors. Untracked all three (they remain as local files for maintainer sessions) and gitignored.claude/so session-local state can never ship again. The block-madtea-api rule's intent (track every raw-API gap) is served by the shipped endpointSuggestions surface instead (#43).