@erclx/canon 4.40.0 → 4.40.1
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.
|
@@ -71,29 +71,29 @@ command -v canon >/dev/null 2>&1
|
|
|
71
71
|
|
|
72
72
|
Before either pipe below, run the scan in `${CLAUDE_SKILL_DIR}/../../standards/publish.md` against the composed block. `.canon/review/` is gitignored, so no hook reaches either write, and this scan is the only gate. The banned-character half runs on both branches, including the local write. The phase-label half applies only on the `--github` branch, where the block reaches a remote.
|
|
73
73
|
|
|
74
|
-
|
|
74
|
+
Local scratch only writes from a toolkit checkout, since `canon feedback` resolves the destination against the toolkit's own `.claude/` folder and a target project never carries one. Pipe the block to `canon feedback --github` first.
|
|
75
75
|
|
|
76
76
|
```bash
|
|
77
|
-
cat <<'EOF' | canon feedback
|
|
77
|
+
cat <<'EOF' | canon feedback --github
|
|
78
78
|
## Toolkit feedback
|
|
79
79
|
|
|
80
80
|
...
|
|
81
81
|
EOF
|
|
82
82
|
```
|
|
83
83
|
|
|
84
|
-
|
|
84
|
+
The CLI opens a GitHub issue on the toolkit repo and prints the issue URL. It needs `gh` authenticated, and falls back to local scratch with the reason on stderr when the call produces no URL and the session holds a toolkit checkout to fall back onto.
|
|
85
85
|
|
|
86
|
-
|
|
86
|
+
From a toolkit checkout, plain `canon feedback` reaches the same destination without opening an issue:
|
|
87
87
|
|
|
88
88
|
```bash
|
|
89
|
-
cat <<'EOF' | canon feedback
|
|
89
|
+
cat <<'EOF' | canon feedback
|
|
90
90
|
## Toolkit feedback
|
|
91
91
|
|
|
92
92
|
...
|
|
93
93
|
EOF
|
|
94
94
|
```
|
|
95
95
|
|
|
96
|
-
|
|
96
|
+
It writes to `.canon/review/feedback/feedback-<slug>-<ts>.md` and prints the absolute path on stdout. Report the printed path back to the user on its own line, in the form the project's instruction file sets under `## Output`.
|
|
97
97
|
|
|
98
98
|
If `canon` is not on PATH, fall back: print the block in chat and tell the user `📋 Copy the block above into a toolkit-repo session.`
|
|
99
99
|
|
|
@@ -102,9 +102,9 @@ If `canon` is not on PATH, fall back: print the block in chat and tell the user
|
|
|
102
102
|
The command exits 1 and writes nothing on a report it refuses, so a non-zero run is a block to repair rather than a report that shipped. Two refusals reach this step:
|
|
103
103
|
|
|
104
104
|
- A named missing field. Add that heading with a real value or its stated fallback, then re-run. Do not report the defect as filed.
|
|
105
|
-
- `gh` absent or its call failed
|
|
105
|
+
- `gh` absent or its call failed. The stderr names which, since installing `gh` and fixing an authenticated call are different repairs. Fall back to printing the block in chat.
|
|
106
106
|
|
|
107
|
-
A `--github` run from a toolkit checkout warns and writes local scratch instead, which is a report filed on the other route rather than a failure.
|
|
107
|
+
A `--github` run from a toolkit checkout whose GitHub call fails warns and writes local scratch instead, which is a report filed on the other route rather than a failure.
|
|
108
108
|
|
|
109
109
|
## Notes
|
|
110
110
|
|