spell 0.8.5 → 0.8.6
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/app/package.json +1 -1
- package/app/spaces/@spell/examples/Solitaire/__project.json5 +22 -4
- package/dist/epic/cli/epicGroups.js +1 -0
- package/dist/epic/command/epicArgs.js +3 -1
- package/dist/epic/comments/ThreadFacts.js +10 -2
- package/dist/epic/components/__pack/epics.entry.js +41 -41
- package/dist/epic/components/__pack/epics.pack.js +1517 -1481
- package/dist/epic/components/epic-answer/EpicAnswer.css +21 -11
- package/dist/epic/components/epic-answer/EpicAnswer.css.inline.js +1 -1
- package/dist/epic/components/epic-item/CollapseAll.css +3 -3
- package/dist/epic/components/epic-item/Fold.js +105 -81
- package/dist/epic/components/epic-overview/EpicOverview.js +0 -2
- package/dist/epic/components/epic-phase/EpicPhase.css +16 -7
- package/dist/epic/components/epic-phase/EpicPhase.css.inline.js +1 -1
- package/dist/epic/components/epic-phase/EpicPhase.js +1 -3
- package/dist/epic/components/epic-section/EpicFold.css +15 -0
- package/dist/epic/components/epic-section/EpicFold.css.inline.js +1 -1
- package/dist/epic/components/epic-section/EpicFold.js +80 -52
- package/dist/epic/components/epic-section/EpicSection.js +1 -3
- package/dist/epic/components/epic-section/EpicSection.types.js +1 -15
- package/dist/epic/components/epic-section/PhaseDrag.js +7 -4
- package/dist/epic/docs/__data/components.json5 +0 -42
- package/dist/epic/docs/epic-overview.html +6 -6
- package/dist/epic/docs/epic-phase.html +12 -5
- package/dist/epic/docs/epic-section.html +6 -4
- package/dist/epic/review/ReviewClient.js +9 -0
- package/dist/epic/tool/InboxCommands.js +12 -1
- package/dist/epic/tool/PLAN-DOC.md +9 -0
- package/dist/epic/tool/PlanDoc.js +17 -5
- package/dist/epic/tool/PlanDocCommands.js +6 -3
- package/dist/epic/tool/ReviewInbox.js +20 -4
- package/dist/epic/tools/_assets/commands.js +452 -451
- package/dist/epic/tools/_assets/core-reference.js +656 -655
- package/dist/epic/tools/_assets/spell-comments.js +575 -569
- package/dist/epic/tools/_assets/spell-doc-runtime.js +16 -3
- package/dist/epic/tools/_assets/spell-syntax.js +415 -414
- package/dist/epic/tools/_assets/spell-ui.entry.js +3 -2
- package/dist/epic/tools/_assets/spell-ui.js +7898 -7835
- package/dist/server/WebServer.js +2 -1
- package/dist/server/liveClient.d.ts +37 -1
- package/dist/server/liveClient.js +119 -6
- package/dist/server/site/PagePatch.d.ts +35 -1
- package/dist/server/site/PagePatch.js +94 -12
- package/dist/ui/components/ui-components/PackHotSwap.d.ts +6 -0
- package/dist/ui/components/ui-components/PackHotSwap.js +12 -2
- package/dist/ui/components/ui-section/UISection.d.ts +8 -0
- package/dist/ui/components/ui-section/UISection.js +22 -11
- package/dist/ui/docs-components/ui-docs-theme-bench/UIDocsThemeBench.d.ts +1 -1
- package/dist/util/spell/constants.js +1 -1
- package/epic/package.json +1 -1
- package/epic/skills/epic/SKILL.md +16 -0
- package/epic/src/AGENTS.md +29 -4
- package/epic/src/tool/PLAN-DOC.md +9 -0
- package/package.json +1 -1
- package/parser/package.json +1 -1
- package/ui/package.json +1 -1
|
@@ -406,6 +406,14 @@ than just being able to move on").
|
|
|
406
406
|
ONE press, I125), or Accept Phase on each (once building: the header's Send is ringed (2px #666) while any waits, its tooltip naming them); one Send. Or he says "go"
|
|
407
407
|
in chat: every waiting plan accepted.
|
|
408
408
|
- Revisit on one: rewrite that plan (a new `--plan` waits again); the accepted ones stay accepted.
|
|
409
|
+
- Accept Phase on one he has just COMMENTED in (its Revisit pressed by itself, I158): the Accept keeps his comments
|
|
410
|
+
(epic `epic-engine` I163; Owen, 2026-10-29: "just incorporate the feedback and auto-approve rather than asking
|
|
411
|
+
me again"). `wait` prints "accepted, with comments to fold in: C4, C5"; `inbox apply` accepts the plan as usual.
|
|
412
|
+
- Fold them into the plan and KEEP it accepted: `epic update <name>#P<N> --plan "<ol>...</ol>" --accepted`
|
|
413
|
+
(no `waiting`, no spinner), then answer each comment on its thread
|
|
414
|
+
(`epic inbox done <name>#C4 --file <answer.html>`: what changed in the plan). NO new Accept, no stop.
|
|
415
|
+
- Only a comment that goes against something he decided, or changes the scope a lot, becomes a Q item instead
|
|
416
|
+
(`epic add <name>#Q`, its thread answered with the link); the rest are still folded in.
|
|
409
417
|
- A plan rewritten from an ANSWER (a question decided, a revisit's pick): the changed words marked
|
|
410
418
|
(`<epic-change item="q<n>">`, then `epic change`), and NO `epic updated` block (epic `epic-engine` I159; Owen,
|
|
411
419
|
2026-10-29, on P51's orange Update under its Q53 marks: "Do we still need the orange update section like this?").
|
|
@@ -428,6 +436,8 @@ than just being able to move on").
|
|
|
428
436
|
(`--plan`, it waits), with the coherence review over it ("4b. Build plans"), listen, and END THE TURN with the
|
|
429
437
|
phase's link pair: "P<N>'s plan changed: ...". Only then a stop.
|
|
430
438
|
- No accepted plan (a phase from before I117, or added without one): write it now, as "4b. Build plans", and wait.
|
|
439
|
+
- Accepted WITH his comments ("accepted, with comments to fold in", epic `epic-engine` I163): fold them in as
|
|
440
|
+
"4b. Build plans" says, `--plan ... --accepted`, answer each comment, and go on. NO stop.
|
|
431
441
|
- No plan at all only when Owen said to start the phase without one ("just do it"), or in bedtime mode.
|
|
432
442
|
2. Do the work.
|
|
433
443
|
Record as you go, not at the end:
|
|
@@ -888,6 +898,11 @@ want you to just do it").
|
|
|
888
898
|
- Up to 5 agents at once (root rules); more: the rest after.
|
|
889
899
|
3. SENT marks: `epic inbox apply <name>`.
|
|
890
900
|
- Approvals, picks and todos made or queued land in the doc; it prints each.
|
|
901
|
+
- An Accept that carries his comments in its text ("accepted, with comments to fold in: C4, C5"; epic
|
|
902
|
+
`epic-engine` I163): `apply` accepts the plan and leaves the comments. Fold them into the plan, keeping it
|
|
903
|
+
accepted (`epic update <name>#P<N> --plan "..." --accepted`), then answer each (`epic inbox done <name>#C4
|
|
904
|
+
--file <answer.html>`). No new Accept. Only a comment against something he decided, or a big change of
|
|
905
|
+
scope, becomes a Q item instead ("4b. Build plans").
|
|
891
906
|
- TEST RESULTS from Owen's test run (epic `epic-engine` P4): `wait` prints them under
|
|
892
907
|
"test, Owen's test run", each test with its result (`passed`, `FAILED`, `skip`, `not now`), his COMMENT and his
|
|
893
908
|
screenshot's path. `apply` applies them all:
|
|
@@ -1351,6 +1366,7 @@ add-phase <name> "Short Name" --symptom .. --changes .. [--goal ..] [--files ..]
|
|
|
1351
1366
|
PN; either way the to-do phases after it move down a number
|
|
1352
1367
|
update <name>#P<N> [--symptom ..] [--changes ..] [--goal ..] [--files ..] [--verify ..] set ("" removes) fields
|
|
1353
1368
|
update <name>#P<N> --plan "<ol>..</ol>" Claude's build plan: waits for Owen's Accept plan (5., step 1)
|
|
1369
|
+
update <name>#P<N> --plan "<ol>..</ol>" --accepted his Accept carried comments: folded in, stays accepted (4b.)
|
|
1354
1370
|
updated <name>#P<N> "<p>what changed</p>" [--summary ".."] [--for <ids>] phase N's plan changed, no item the
|
|
1355
1371
|
cause: <epic-update>, after Goal; nothing when marks say it
|
|
1356
1372
|
file <name>#P<N> <rN> a request into phase N's Requests field, marked filed there
|
package/epic/src/AGENTS.md
CHANGED
|
@@ -97,9 +97,18 @@ Only what's local is below; a section named like a WWOD rule extends it.
|
|
|
97
97
|
- a section's badge and tools stay beside its title while the title fits on one line beside them; only when it
|
|
98
98
|
doesn't (the side bar, a phone) do they wrap, together, onto a row of their own at its end (epic `epic-engine`
|
|
99
99
|
I149: under 480px they always did before)
|
|
100
|
-
- collapse-all
|
|
101
|
-
|
|
102
|
-
|
|
100
|
+
- no expand-all or collapse-all button in a title row (epic `epic-engine` I161; Owen, 2026-10-29: "combine the
|
|
101
|
+
'expand/collapse all' with the normal disclosure triangle -- holding down option is 'expand all'"):
|
|
102
|
+
- ⌥-click (Alt-click) on any fold's chevron or title, or ⌥+Enter / ⌥+Space on its focused chevron, opens it and
|
|
103
|
+
everything in it, cards too, parts loading as they open (`expandAll()`); on an open one, folds everything
|
|
104
|
+
in it, then itself (`Fold.toggleFrom()`, `EpicFold.toggleDeep()`)
|
|
105
|
+
- every chevron's tooltip ends with what ⌥-click does (`DEEP_TIPS`; `<ui-section>`'s `toggleTipMore`)
|
|
106
|
+
- the Log stays folded under it, as under the page's expand-all (`staysFolded`, I155)
|
|
107
|
+
- the page toolbar keeps its one toggle-all (`Fold.toggleAllButton()`): it has no chevron to hold
|
|
108
|
+
- its cursors (I161; Owen: "pointer when over content in these headers, drag cursor when over whitespace"):
|
|
109
|
+
the fold button is only as wide as its chevron, icon and title; the pointer over those, the badge and the
|
|
110
|
+
buttons; over the row's empty space, the pointer too (a click there folds it, `onTitleRowClick()`), but the grab
|
|
111
|
+
cursor on a to-do phase while the page is reviewed (`PhaseDrag`), grabbing while one is dragged
|
|
103
112
|
- CSS and the elements' own drawing only: the page's markup is unchanged, so no migration step
|
|
104
113
|
- NOT `<ui-section>` on guides: at phone width a title there still runs on under its buttons,
|
|
105
114
|
fading out (`spell-doc.css`; Owen, 2026-10-10: "stay in place and overlap")
|
|
@@ -1287,6 +1296,9 @@ In `tools/`:
|
|
|
1287
1296
|
- The patch is the kit's ONE patcher (`PagePatch`, `spell/server/site`; epic `epic-engine` P40), with this
|
|
1288
1297
|
runtime's rules (`patcher`): a list of small steps, text edited in place; the page comes with the change.
|
|
1289
1298
|
- Scroll, folds, open panels and typed text stay.
|
|
1299
|
+
- Shown as ONE short cross-fade when it changes what's on screen (`patcher.redraw()`, the kit's `PagePatch.crossFade()`;
|
|
1300
|
+
epic `epic-engine` I164): never a half-drawn frame; straight in when it's off screen, motion is reduced, or a
|
|
1301
|
+
field has the focus.
|
|
1290
1302
|
- Anything the runtime adds inside `main` must carry `data-spell-added`, so the patch steps around it.
|
|
1291
1303
|
- Pages with scripts of their own still reload.
|
|
1292
1304
|
Inert data blocks (`<script type="text/plain">`) don't count.
|
|
@@ -1301,6 +1313,9 @@ In `tools/`:
|
|
|
1301
1313
|
- every fold open before it, items and a link's unfolds too:
|
|
1302
1314
|
this runtime keeps them as the page goes (`keepFoldsForReload()`, `sessionStorage`)
|
|
1303
1315
|
- a half-written note (the review inbox's drafts) and comment drafts (`localStorage`)
|
|
1316
|
+
- with no flash (epic `epic-engine` I164): the new page waits behind the old one (the kit's `holdReveal()`, a
|
|
1317
|
+
cross-document view transition) until this runtime has landed and the page wears its theme
|
|
1318
|
+
(`SpellUI.themed`), then cross-fades in: `SPELL_SERVER.reveal()`
|
|
1304
1319
|
- not while you type in a field: an "Updated: reload" pill waits, and it reloads once you leave the field
|
|
1305
1320
|
- so a merge's new widgets show up by themselves: VS Code's window needs reloading only when the EXTENSION changes
|
|
1306
1321
|
- `<body>`'s attributes are patched too.
|
|
@@ -1312,6 +1327,8 @@ In `tools/`:
|
|
|
1312
1327
|
- an epic page's `<epic-*>` blocks and items: a split epic page's parts (`wireSourceBodies()`)
|
|
1313
1328
|
- The patch leaves what a host loaded alone.
|
|
1314
1329
|
- A changed body file (the live client's `spell-server:changed`) re-fetches its open host in place.
|
|
1330
|
+
- the old body stays up until the new one is in, then one short cross-fade (`PagePatch.crossFade()`, at most
|
|
1331
|
+
`BODY_WAIT_MS`), when the host is on screen
|
|
1315
1332
|
- Each body that loads re-runs the outline, the toolbar, counts, item filters and code colors.
|
|
1316
1333
|
- A link to an id inside an unloaded body loads it first.
|
|
1317
1334
|
The ids are in its host's `data-part-ids`, or an `<epic-*>` host's `part-ids`.
|
|
@@ -1591,7 +1608,14 @@ Each kind of page has ONE name, written everywhere a person reads it.
|
|
|
1591
1608
|
comments: ["c4"] }`
|
|
1592
1609
|
- a revisit: the comment joins its `comments`, its note's last line names them all (`withInlineComments()`)
|
|
1593
1610
|
- a pick: that revisit, carrying the pick ("pick B, but ...")
|
|
1594
|
-
-
|
|
1611
|
+
- an Approve / Accept plan: still approved, the comment joining its `comments` (epic `epic-engine` I163)
|
|
1612
|
+
- any other mark (Make Todo, a revisit asked now): left alone
|
|
1613
|
+
- APPROVE on such a revisit (Approve, Accept Phase, Accept plan; epic `epic-engine` I163; Owen, 2026-10-29: "just
|
|
1614
|
+
incorporate the feedback and auto-approve rather than asking me again") keeps them (`ReviewClient.press()`):
|
|
1615
|
+
`{ action: "approve", note, comments }`; clicked again, the revisit again
|
|
1616
|
+
- `wait` prints "accepted, with comments to fold in: C4, C5"; `inbox apply` accepts the plan, the comments
|
|
1617
|
+
left waiting; Claude folds them in with `update <name>#P<n> --plan ... --accepted` (written accepted, no
|
|
1618
|
+
second Accept) and answers each
|
|
1595
1619
|
- deleted or cleared (`dropComment()`): out of every revisit naming it; nothing left in one (no comment, no words
|
|
1596
1620
|
of Owen's): a pick goes back to the plain pick, else the mark goes
|
|
1597
1621
|
- Send counts one mark and the comment; `wait` hands the comment over once, inside the revisit
|
|
@@ -2011,6 +2035,7 @@ Each kind of page has ONE name, written everywhere a person reads it.
|
|
|
2011
2035
|
- the bullhorn (a green check circle once done)
|
|
2012
2036
|
- its id, `C3`: small and muted, an outline and no fill (epic `epic-workflow` P23; `M3` until `epic-engine` P44)
|
|
2013
2037
|
- the pane's summary (`ThreadFacts.headline()`): the quote's first words, else the block's; its tooltip the full place
|
|
2038
|
+
- a saved thread's header: the start of Owen's own words instead (I162): the page highlights what was selected
|
|
2014
2039
|
- No date: each message has its time.
|
|
2015
2040
|
- Then OWEN'S ANSWER, while it's his turn: an epic page item's review pills
|
|
2016
2041
|
("same semantics/look as pills in item header").
|
|
@@ -191,6 +191,15 @@ As `plan-doc.md`, "Ids":
|
|
|
191
191
|
(`<epic-review buttons="plan">`).
|
|
192
192
|
- Accept plan is the inbox mark `approve` on the phase; `inbox apply` writes the field's `accepted` (now) and
|
|
193
193
|
`plan="accepted"` (`PlanDoc.acceptPlan()`): "plan accepted: build it".
|
|
194
|
+
- Accept plan pressed on a phase whose text holds Owen's comments (its auto revisit, I158) KEEPS them (epic
|
|
195
|
+
`epic-engine` I163): the mark `{ action: "approve", note, comments: ["c4", "c5"] }`; a comment saved on a phase
|
|
196
|
+
already approved joins it, still approved (`ReviewInbox.noteComment()`).
|
|
197
|
+
- `wait` prints "accepted, with comments to fold in: C4, C5", each comment under it; `inbox apply` accepts the
|
|
198
|
+
plan as usual ("plan accepted: build it, with comments to fold in: C4, C5") and leaves the comments waiting.
|
|
199
|
+
- Claude folds them in and keeps it accepted: `update <name>#P3 --plan "..." --accepted` writes the plan
|
|
200
|
+
`accepted` (logged `P3 plan written: accepted, Owen's comments folded in`), no `waiting`, no spinner; then
|
|
201
|
+
answers each comment. Without `--accepted`, `--plan` waits as before.
|
|
202
|
+
- Only a comment against something he decided, or changing the scope a lot, becomes a Q item instead.
|
|
194
203
|
- Children in that order, always (the vocabulary's `childOrder: "listed"`):
|
|
195
204
|
the tool puts each where it belongs.
|
|
196
205
|
- Owen's kept notes (`<epic-reply>`) after Requests, before Goal; slotted children (status cards) at the end.
|
package/package.json
CHANGED
package/parser/package.json
CHANGED