Catcrafts/Crafter.Review
Watch
2
0
Fork
You've already forked Crafter.Review
 0
Code Issues 7 Pull requests Projects Releases 3 Packages Wiki Activity Actions
Crafter.Review/process/templates/config.json

114 lines
2.1 KiB
JSON
Raw Normal View History

feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
{
"base": "origin/main",
"rangeFrom": "upstream",
"authors": [
"you@example.com"
],
"aiTrailers": "forbid",
"requireSigned": false,
"allowDirty": [],
"gate0": [
"make check"
],
"lenses": {
"repo-better-solution": {
feat(config): every lens off until the repository turns it on Jorijn: "all lenses off by default and opt in only". Config::Defaults() gives every lens run: false; a config that turns on none - a missing `lenses` key included - has the one problem that names the lenses, so config, freeze and run all stop on it; the template ships every lens off, init says to turn lenses on, and the "no lens runs" preflight names the cause. A consumer config without a `lenses` key now needs one, as the CI smoke test's does. Proven with the lens commit before it: the suite (26 passed), and the dry-run comparison recorded there.
2026-10-31 20:09:07 +01:00
"run": false,
feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
"environment": "none"
},
"repo-functional": {
feat(config): every lens off until the repository turns it on Jorijn: "all lenses off by default and opt in only". Config::Defaults() gives every lens run: false; a config that turns on none - a missing `lenses` key included - has the one problem that names the lenses, so config, freeze and run all stop on it; the template ships every lens off, init says to turn lenses on, and the "no lens runs" preflight names the cause. A consumer config without a `lenses` key now needs one, as the CI smoke test's does. Proven with the lens commit before it: the suite (26 passed), and the dry-run comparison recorded there.
2026-10-31 20:09:07 +01:00
"run": false,
feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
"environment": "browser"
},
"repo-bug-prover": {
feat(config): every lens off until the repository turns it on Jorijn: "all lenses off by default and opt in only". Config::Defaults() gives every lens run: false; a config that turns on none - a missing `lenses` key included - has the one problem that names the lenses, so config, freeze and run all stop on it; the template ships every lens off, init says to turn lenses on, and the "no lens runs" preflight names the cause. A consumer config without a `lenses` key now needs one, as the CI smoke test's does. Proven with the lens commit before it: the suite (26 passed), and the dry-run comparison recorded there.
2026-10-31 20:09:07 +01:00
"run": false,
feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
"environment": "none"
},
"repo-security": {
feat(config): every lens off until the repository turns it on Jorijn: "all lenses off by default and opt in only". Config::Defaults() gives every lens run: false; a config that turns on none - a missing `lenses` key included - has the one problem that names the lenses, so config, freeze and run all stop on it; the template ships every lens off, init says to turn lenses on, and the "no lens runs" preflight names the cause. A consumer config without a `lenses` key now needs one, as the CI smoke test's does. Proven with the lens commit before it: the suite (26 passed), and the dry-run comparison recorded there.
2026-10-31 20:09:07 +01:00
"run": false,
feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
"environment": "none"
feat(lenses): the commit-truth lens, repo-facts, as Gate 4 Every claim in every commit message, and in the documentation the range adds or changes, proven or gone. The lens's block kinds are text, doc and slot: a message unit is keyed on its text, the base and the code up to its commit (MessageDeps); a documentation unit on its file, its normalised text, the base and the code of the whole range (DocKeyParts); a diffstat on its text alone; whole:order and whole:absent are asked in slot passes of its own, never stored. A documentation file's diff header and a part the commit writes nothing in are a mechanical n/a. Budgets 60/40 for a text or doc block, 50/35 for a slot; one read. Gate 4, after the proofs, so the messages and documents are read once the code they describe has settled; the owner's gate is 5. The goldens that follow from the lens table are derived by tests/Goldens/derive.py, which asserts that the recorded table still reproduces the recorded entries before it writes. Proven, with the opt-in commit after this one: the suite (26 passed); a dry run of a scratch range (2 commits, a README with sections) by the previous binary and this one with the three static lenses on and the rest off, 25 prompts and 4 system files byte for byte; with repo-facts on as well, those files unchanged and 10 passes and 1 system file added. The lens's firing proof in this pipeline is owed (the owner's go).
2026-10-31 20:08:26 +01:00
},
"repo-facts": {
feat(config): every lens off until the repository turns it on Jorijn: "all lenses off by default and opt in only". Config::Defaults() gives every lens run: false; a config that turns on none - a missing `lenses` key included - has the one problem that names the lenses, so config, freeze and run all stop on it; the template ships every lens off, init says to turn lenses on, and the "no lens runs" preflight names the cause. A consumer config without a `lenses` key now needs one, as the CI smoke test's does. Proven with the lens commit before it: the suite (26 passed), and the dry-run comparison recorded there.
2026-10-31 20:09:07 +01:00
"run": false,
feat(lenses): the commit-truth lens, repo-facts, as Gate 4 Every claim in every commit message, and in the documentation the range adds or changes, proven or gone. The lens's block kinds are text, doc and slot: a message unit is keyed on its text, the base and the code up to its commit (MessageDeps); a documentation unit on its file, its normalised text, the base and the code of the whole range (DocKeyParts); a diffstat on its text alone; whole:order and whole:absent are asked in slot passes of its own, never stored. A documentation file's diff header and a part the commit writes nothing in are a mechanical n/a. Budgets 60/40 for a text or doc block, 50/35 for a slot; one read. Gate 4, after the proofs, so the messages and documents are read once the code they describe has settled; the owner's gate is 5. The goldens that follow from the lens table are derived by tests/Goldens/derive.py, which asserts that the recorded table still reproduces the recorded entries before it writes. Proven, with the opt-in commit after this one: the suite (26 passed); a dry run of a scratch range (2 commits, a README with sections) by the previous binary and this one with the three static lenses on and the rest off, 25 prompts and 4 system files byte for byte; with repo-facts on as well, those files unchanged and 10 passes and 1 system file added. The lens's firing proof in this pipeline is owed (the owner's go).
2026-10-31 20:08:26 +01:00
"environment": "none"
feat(modes): the kernel modes - a patch series and a mailing-list reply Beside the push gates, crafter-review runs the pre-send review of a kernel contributor's workbench: --mode series over a format-patch export with its cover letter, --mode reply over a mail draft. The inventory partitions a cover letter, a plain mail and the camera review's shape; ten kernel lenses join the table with their gates (structure, code, artifact truth) and the persona gate - one maintainer-persona instance per --reviewers entry, its whole pass gating its blocks and pruning the units that are not theirs. A series' code units are keyed on the code like the push gates'; every text unit on its text, the references it cites and the anchor when it is dated. The references an artifact cites are prefetched through utilities/lore.py into the gate-state, with a digest in the run layer, and a persona's calibration map is its lore listing. The kernel schema carries the persona vocabulary, the kernel note kinds, the predicted review and the not-mine list; the matrix the persona holes, the thin and the modelled units; gates clean without a persona pass is GATES CLEAN. A reply's gate-state sits beside the draft and is read once; a kernel mode needs --subsystem, defaults the effort to max and the trees to work/linux,work/milos-linux, and excuses no unit from the holes. The kernel lenses and the common text ship verbatim; the table lists them after the push gates' lenses and the config template holds them off, so a repository that never turns them on changes nothing. Prompts, keys and plans were checked byte for byte against the pipeline these modes replace, on its own artifacts: two replies and a series, every system prompt, user prompt, job and reuse key identical.
2026-10-31 22:56:12 +01:00
},
"better-solution": {
"run": false,
"environment": "none"
},
"code-quality": {
"run": false,
"environment": "none"
},
"minimalism": {
"run": false,
"environment": "none"
},
"bug-prover": {
"run": false,
"environment": "none"
},
"facts": {
"run": false,
"environment": "none"
},
"consistency": {
"run": false,
"environment": "none"
},
"process-docs": {
"run": false,
"environment": "none"
},
"etiquette": {
"run": false,
"environment": "none"
},
"conciseness": {
"run": false,
"environment": "none"
},
"maintainer-persona": {
"run": false,
"environment": "none"
feat(core): the data home, the lens texts, and --version naming both process/ holds the procedure, the five lens texts, the templates and the skill under process/skill/prepush/. A lens text's sha256 is part of every reuse key and the texts are part of every prompt, so they carry no SPDX header; --version prints the charter hashes: 1728bd4c, 148d5c4c, c7ffef44 and 2b9a5f83 for the four charters. Home() finds them: CRAFTER_REVIEW_HOME, natively only (a host setting must not swap the Flatpak's texts for a checkout's), then <exe>/../share/crafter-review, then the checkout the binary was built in. Main() hands `__supervise` to the supervisor before anything else, then decides the sandbox once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 05:51:37 +01:00
}
},
"supabase": {
"dbUrl": "postgresql://postgres:postgres@127.0.0.1:54322/postgres",
"start": null,
"stop": null,
"notes": ""
},
"slots": {
"dir": null,
"start": null,
"stop": null,
"memMb": null,
"startMb": null
},
"functional": {
"appUrl": "http://localhost:8080",
"readyPath": "/",
"apiUrls": [],
"start": "make run",
"stop": "make stop",
"login": {
"fixtures": [
".local-stack/test-user.json"
],
"notes": "the fixture holds a TOTP-verified login"
},
"exclude": [
"**/*.test.*",
"**/*.spec.*",
"docs/**",
".github/**",
"*.md"
],
"extraTools": [],
"mcp": {
"command": "npx",
"args": null
},
"notes": ""
}
}
Reference in a new issue Copy permalink