@hanzlaa/rcode 4.10.4 → 4.10.5
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.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hanzlaa/rcode",
|
|
3
|
-
"version": "4.10.
|
|
3
|
+
"version": "4.10.5",
|
|
4
4
|
"description": "rcode — the AI team that never forgets. Persistent memory, specialist agents, and slash commands for AI IDEs. Works in Claude Code, Cursor, Gemini, VS Code, and Antigravity.",
|
|
5
5
|
"main": "cli/index.js",
|
|
6
6
|
"bin": {
|
|
@@ -5,11 +5,21 @@ Run this check at the very start of any workflow that needs project state.
|
|
|
5
5
|
## Step: Detect project initialization
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
|
-
|
|
8
|
+
if [ ! -f .rcode/config.yaml ]; then
|
|
9
|
+
echo "rcode-not-initialized"
|
|
10
|
+
elif grep -q "Generated by install" .rcode/config.yaml 2>/dev/null && [ ! -f .rcode/JOURNEY.md ]; then
|
|
11
|
+
echo "rcode-seeded-not-configured"
|
|
12
|
+
else
|
|
13
|
+
echo "rcode-ready"
|
|
14
|
+
fi
|
|
9
15
|
```
|
|
10
16
|
|
|
17
|
+
**Why the middle case matters (confirmed live, issue class closed by #1034-#1036's fixes):** `rcode install` pre-seeds `config.yaml` with installer defaults (`user_name: "$USER"`, `mode: "guided"`, etc.) so the tool has something to read before the user ever runs `/rcode-init`. A plain `test -f .rcode/config.yaml` check can't tell "the user was actually asked their preferences" apart from "the installer wrote plausible-looking defaults nobody confirmed" — both produce a config.yaml that exists. `/rcode-init` itself distinguishes these correctly (via its own `JOURNEY.md`-presence check), but every OTHER workflow that dispatches through this lightweight guard (e.g. `/rcode-do`) was checking existence only, so a user routed entirely through `/rcode-do` could go through many sessions on installer defaults, never once asked their name/language/mode/model-profile — while a user who happened to run `/rcode-init` directly got asked properly. That inconsistency is now closed: `rcode-seeded-not-configured` routes to the same question flow as `rcode-not-initialized` below, just skipping the bin-bootstrap step (already done by install).
|
|
18
|
+
|
|
11
19
|
**If `rcode-ready`:** continue with the workflow normally.
|
|
12
20
|
|
|
21
|
+
**If `rcode-seeded-not-configured`:** skip Step 1 (bin bootstrap — install already did this) and go straight to Step 2 (ask the 5 config questions) below, then continue with Steps 3-6 as written (Step 3's `.rcode/config.yaml` write overwrites the installer-seeded stub with real answers).
|
|
22
|
+
|
|
13
23
|
**If `rcode-not-initialized`:** the user has never set up rcode for this project. Do NOT fail or continue blindly. Run the project init flow inline before proceeding:
|
|
14
24
|
|
|
15
25
|
---
|