housebroken-cli 0.9.0__tar.gz → 0.9.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/PKG-INFO +2 -2
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/README.md +1 -1
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/pyproject.toml +1 -1
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/file-pr.sh +18 -5
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/skills/housebroken/SKILL.md +2 -1
- housebroken_cli-0.9.1/src/housebroken/__init__.py +1 -0
- housebroken_cli-0.9.0/src/housebroken/__init__.py +0 -1
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/.gitignore +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/LICENSE +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/bin/housebroken +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/hatch_build.py +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/branch-check.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/check-ai-policy.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/claim-check.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/comment-census.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/comment-check.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/declare.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/diff-defaults.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/distinct-outside.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/file-issue.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/fork-hygiene.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/gate-hook.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/inbox.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/notes.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/pr-sweep.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/prior-art.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/proof.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/push.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/ref-check.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/reply.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/review.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/scripts/verify-filed-pr.sh +0 -0
- {housebroken_cli-0.9.0 → housebroken_cli-0.9.1}/src/housebroken/cli.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: housebroken-cli
|
|
3
|
-
Version: 0.9.
|
|
3
|
+
Version: 0.9.1
|
|
4
4
|
Summary: Agent-written pull requests that do not make a mess in someone else's house.
|
|
5
5
|
Project-URL: Repository, https://github.com/lenamonj/housebroken
|
|
6
6
|
License-Expression: MIT
|
|
@@ -78,7 +78,7 @@ A memory-safety, remote-abort, injection or path-escape finding goes by the proj
|
|
|
78
78
|
**9. File through the gate.**
|
|
79
79
|
`branch-check.sh` refuses a dirty working tree, a file whose mode disagrees with its siblings, a file the repository's own `.gitignore` excludes, a working artifact, a commit carrying a tool trailer, a session link or a tool identity, a sign-off naming a username, a branch not on top of its base, any comment added to code, a warning suppression that does not name what it hides or that no build log shows firing, reflection added to a .NET project that declares AOT or trim support without an AOT publish log of it, a credential or a path under your own home, a lockfile, generated file or binary nobody named, an agent's working file, and a file rewritten for its line endings; it notes a base the upstream has moved past, a user path that may be a fixture and every absolute claim in added prose, and stamps the head it passed.
|
|
80
80
|
`review.sh` names the adversarial reviewer: a different model from the one that wrote the change, one tier down, never below Sonnet. Before it runs, the author writes a declaration (`declare.sh`): what the change was not tested against, and every assumption with what breaks if it is wrong and how it was checked. "Nothing" is refused as an answer. The review reads the declaration as one of its texts and attacks each line. The reviewer gets a fresh context, hard read-only limits, and before it reads the diff it writes its own fix from the bug alone, so it is not anchored on ours; the report names that fix as a diff and the gate refuses one that does not, a POST AS IS over an open BLOCKING or SHOULD FIX finding, and a POST AS IS over items the reviewer skipped. Its attack list starts with every claim the prose makes and includes the form of the code: the reviewer writes the changed block the way the strongest engineer in that language would, in the repository's own idioms, and a smaller or clearer version is a finding; every finding carries evidence it produced itself, and its report is bound to the head and the text it read. A fix is a new head and gets a new review.
|
|
81
|
-
`file-pr.sh` is the only way a pull request is opened. It refuses without a prior-art printout under a day old that searched every file the branch changes, a policy printout under a day old that reads neither BAN nor UNREAD, a body that discloses when the policy asks and runs under 120 words of its own beside the project's template, a branch stamp for the exact head whose base the upstream has not since changed under the branch's files, a proof stamp for that head, a declaration that passes, a POST AS IS review of that head, that body and that declaration, fewer than three open pull requests of yours on the repository, and ten minutes since the last.
|
|
81
|
+
`file-pr.sh` is the only way a pull request is opened. It refuses without a prior-art printout under a day old that searched every file the branch changes, a policy printout under a day old that reads neither BAN nor UNREAD, a body that discloses when the policy asks and runs under 120 words of its own beside the project's template (the answer to the template's AI question counted apart, at most 50), a branch stamp for the exact head whose base the upstream has not since changed under the branch's files, a proof stamp for that head, a declaration that passes, a POST AS IS review of that head, that body and that declaration, fewer than three open pull requests of yours on the repository, and ten minutes since the last.
|
|
82
82
|
`file-issue.sh` is the only way an issue is opened. It refuses without the same prior-art and policy printouts, refuses the same prose, and refuses a body that mentions a fix, a patch or a pull request without a GitHub link to the branch or commit, so work that exists is attributable to whoever did it.
|
|
83
83
|
|
|
84
84
|
**10. Watch it land.**
|
|
@@ -66,7 +66,7 @@ A memory-safety, remote-abort, injection or path-escape finding goes by the proj
|
|
|
66
66
|
**9. File through the gate.**
|
|
67
67
|
`branch-check.sh` refuses a dirty working tree, a file whose mode disagrees with its siblings, a file the repository's own `.gitignore` excludes, a working artifact, a commit carrying a tool trailer, a session link or a tool identity, a sign-off naming a username, a branch not on top of its base, any comment added to code, a warning suppression that does not name what it hides or that no build log shows firing, reflection added to a .NET project that declares AOT or trim support without an AOT publish log of it, a credential or a path under your own home, a lockfile, generated file or binary nobody named, an agent's working file, and a file rewritten for its line endings; it notes a base the upstream has moved past, a user path that may be a fixture and every absolute claim in added prose, and stamps the head it passed.
|
|
68
68
|
`review.sh` names the adversarial reviewer: a different model from the one that wrote the change, one tier down, never below Sonnet. Before it runs, the author writes a declaration (`declare.sh`): what the change was not tested against, and every assumption with what breaks if it is wrong and how it was checked. "Nothing" is refused as an answer. The review reads the declaration as one of its texts and attacks each line. The reviewer gets a fresh context, hard read-only limits, and before it reads the diff it writes its own fix from the bug alone, so it is not anchored on ours; the report names that fix as a diff and the gate refuses one that does not, a POST AS IS over an open BLOCKING or SHOULD FIX finding, and a POST AS IS over items the reviewer skipped. Its attack list starts with every claim the prose makes and includes the form of the code: the reviewer writes the changed block the way the strongest engineer in that language would, in the repository's own idioms, and a smaller or clearer version is a finding; every finding carries evidence it produced itself, and its report is bound to the head and the text it read. A fix is a new head and gets a new review.
|
|
69
|
-
`file-pr.sh` is the only way a pull request is opened. It refuses without a prior-art printout under a day old that searched every file the branch changes, a policy printout under a day old that reads neither BAN nor UNREAD, a body that discloses when the policy asks and runs under 120 words of its own beside the project's template, a branch stamp for the exact head whose base the upstream has not since changed under the branch's files, a proof stamp for that head, a declaration that passes, a POST AS IS review of that head, that body and that declaration, fewer than three open pull requests of yours on the repository, and ten minutes since the last.
|
|
69
|
+
`file-pr.sh` is the only way a pull request is opened. It refuses without a prior-art printout under a day old that searched every file the branch changes, a policy printout under a day old that reads neither BAN nor UNREAD, a body that discloses when the policy asks and runs under 120 words of its own beside the project's template (the answer to the template's AI question counted apart, at most 50), a branch stamp for the exact head whose base the upstream has not since changed under the branch's files, a proof stamp for that head, a declaration that passes, a POST AS IS review of that head, that body and that declaration, fewer than three open pull requests of yours on the repository, and ten minutes since the last.
|
|
70
70
|
`file-issue.sh` is the only way an issue is opened. It refuses without the same prior-art and policy printouts, refuses the same prose, and refuses a body that mentions a fix, a patch or a pull request without a GitHub link to the branch or commit, so work that exists is attributable to whoever did it.
|
|
71
71
|
|
|
72
72
|
**10. Watch it land.**
|
|
@@ -48,7 +48,8 @@ gates:
|
|
|
48
48
|
RESULT: DISCLOSE the body must name the AI use
|
|
49
49
|
prose no tool footer, session trailer, co-author trailer, em dash or
|
|
50
50
|
en dash, in any case, in the --body-file or the --title; a
|
|
51
|
-
body of at most 120 words
|
|
51
|
+
body of at most 120 words of its own, the answer to the
|
|
52
|
+
template's AI question counted apart and held to 50
|
|
52
53
|
branch $HOUSEBROKEN_HOME/branch-checks/<head> must exist, written by
|
|
53
54
|
branch-check.sh when this head passed, against the branch this
|
|
54
55
|
files into (--base, or the repository's default branch)
|
|
@@ -160,19 +161,31 @@ check_text "body file $bodyfile" "$(cat "$bodyfile")"
|
|
|
160
161
|
check_text "--title" "$title"
|
|
161
162
|
# The project's own template text is kept verbatim and is not ours to count:
|
|
162
163
|
# HTML comments and every line the saved template carries, a ticked box read
|
|
163
|
-
# as its unticked line, are left out before the words are counted.
|
|
164
|
+
# as its unticked line, are left out before the words are counted. The
|
|
165
|
+
# answer written after a template line that asks about AI is the project's
|
|
166
|
+
# requirement, not ours: it is counted on its own and held to 50 words.
|
|
164
167
|
template="$home/policy/template-${repo%%/*}-${repo##*/}.md"
|
|
165
168
|
[ -f "$template" ] || template=/dev/null
|
|
166
|
-
words
|
|
169
|
+
read -r words ai_words < <(awk -v T="$template" '
|
|
167
170
|
function norm(s) { gsub(/\[[xX]\]/, "[ ]", s); gsub(/^[[:space:]]+|[[:space:]]+$/, "", s); return s }
|
|
168
171
|
BEGIN { while ((getline l < T) > 0) { l = norm(l); if (l != "") t[l] = 1 } }
|
|
169
172
|
{ l = norm($0); if (l in t) next
|
|
170
|
-
|
|
171
|
-
|
|
173
|
+
best = ""
|
|
174
|
+
for (k in t) if (index(l, k) == 1 && length(k) > length(best)) best = k
|
|
175
|
+
if (best != "") {
|
|
176
|
+
l = substr(l, length(best) + 1)
|
|
177
|
+
if (tolower(best) ~ /(^|[^a-z])ai([^a-z]|$)|artificial intelligence|generative|llm|language model/) { ai += split(l, w); next }
|
|
178
|
+
}
|
|
179
|
+
ours += split(l, w) }
|
|
180
|
+
END { print ours + 0, ai + 0 }' "$bodyfile")
|
|
172
181
|
if [ "$words" -gt 120 ]; then
|
|
173
182
|
echo "REFUSED: the body is $words words outside the project's template - say what was wrong, what the change does and how it was verified in 120 or fewer" >&2
|
|
174
183
|
exit 2
|
|
175
184
|
fi
|
|
185
|
+
if [ "$ai_words" -gt 50 ]; then
|
|
186
|
+
echo "REFUSED: the answer to the template's AI question is $ai_words words - name the tool and what it did in 50 or fewer" >&2
|
|
187
|
+
exit 2
|
|
188
|
+
fi
|
|
176
189
|
if [ "$policy_result" = "DISCLOSE" ] && ! grep -qiE '\bAI\b|LLM|Claude|Copilot|ChatGPT|language model|assist' "$bodyfile"; then
|
|
177
190
|
echo "REFUSED: $repo requires AI use to be disclosed ($policy) and the body does not name it" >&2
|
|
178
191
|
exit 2
|
|
@@ -144,7 +144,8 @@ report it in one line and do not proceed to the next step.
|
|
|
144
144
|
file may open with the licence header its neighbours carry, and a
|
|
145
145
|
maintainer's explicit request for documentation is the one exception,
|
|
146
146
|
passed as `--asked <URL of the request>`. The body is under 120 words,
|
|
147
|
-
in the project's template if it has one
|
|
147
|
+
in the project's template if it has one (the answer to the template's
|
|
148
|
+
own AI question is counted apart, at most 50 words), and says what was wrong, what the
|
|
148
149
|
change does, and how it was verified; every sentence in it is something
|
|
149
150
|
you reproduced on the fresh clone in this session, never a line carried
|
|
150
151
|
from a journal. No tool footer, no session link, no
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
__version__ = "0.9.1"
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
__version__ = "0.9.0"
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|