@skyf0xx/hedgehog 3.0.10 → 3.0.11
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/README.md
CHANGED
|
@@ -48,6 +48,18 @@ The build order is encoded into the project. The AI does not have to remember wh
|
|
|
48
48
|
|
|
49
49
|
|
|
50
50
|
|
|
51
|
+
## Your build order is a graph
|
|
52
|
+
|
|
53
|
+
**Every task** Hedgehog generates **is a node** with explicit dependencies in sqlite.
|
|
54
|
+
|
|
55
|
+
Unlike stories and epics, **the graph locks build order** into an **signal-dense, context-light** path the agents can use.
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
npx @skyf0xx/hedgehog graph
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
|
|
62
|
+
|
|
51
63
|
## What Hedgehog builds
|
|
52
64
|
|
|
53
65
|
### Full-stack applications
|
|
@@ -156,15 +168,6 @@ from them. It never touches the instructions file, the build graph, the
|
|
|
156
168
|
core workspace, or `skills/BMAD`, since those carry project-specific or
|
|
157
169
|
write-once content.
|
|
158
170
|
|
|
159
|
-
To see the build graph:
|
|
160
|
-
|
|
161
|
-
``` bash
|
|
162
|
-
npx @skyf0xx/hedgehog graph
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
Starts a small local server and opens a live, read-only diagram of every
|
|
166
|
-
task, status and its dependencies.
|
|
167
|
-
|
|
168
171
|
## Why Hedgehog
|
|
169
172
|
|
|
170
173
|
Most AI coding tools improve prompting.
|
package/package.json
CHANGED
|
@@ -15,9 +15,16 @@ schedule — the orchestration wiring: what runs when, retries, backfill entry
|
|
|
15
15
|
|
|
16
16
|
## Adaptation points
|
|
17
17
|
|
|
18
|
-
-
|
|
19
|
-
|
|
20
|
-
|
|
18
|
+
- On the Dagster stack, `schedule` is Dagster's own schedule/sensor
|
|
19
|
+
definitions plus the retry policy on each op — real orchestration
|
|
20
|
+
surface that belongs in this repo and earns its own layer.
|
|
21
|
+
- On the stdlib/argparse stack, or when a pipeline is invoked externally
|
|
22
|
+
regardless of stack (cron calling a script, an orchestrator defined
|
|
23
|
+
outside this repo), there is no in-repo orchestrator to retry or
|
|
24
|
+
backfill through: merge `schedule` into `load` and scope it to
|
|
25
|
+
whatever the script itself can do (an idempotent upsert key, a
|
|
26
|
+
`--since`/`--backfill` flag `load` reads), and record retries/
|
|
27
|
+
scheduling as owned by the caller rather than as a gap in this layer.
|
|
21
28
|
- Split `extract` per source (`extract/{module}`) when the pipeline pulls
|
|
22
29
|
from several genuinely different systems with independent failure modes
|
|
23
30
|
and auth; keep one `extract` layer for a single source.
|