mapples 0.2.0-beta.4 → 0.2.0-beta.6

package/templates/claude/skills/mapples-design/reference/playbooks/navigation-chrome.md

@@ -0,0 +1,21 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Navigation chrome
+
+Headers, tab bars, chips, badges and breadcrumbs: navigator options vs content-sized elements.
+
+Two kinds of chrome, two mechanisms — never mix them up:
+- Stack headers and tab bars belong to the NAVIGATOR. In this version they are set in Creator (navigator options: header visible/title/colors/back, tab bar colors/labels; route options: title, tab label, tab icon asset) and land in the CLI-owned `_layout.tsx` on the next sync — you cannot set them from code, and you must not edit the layouts. Describe the intended chrome per section in `design.md` under `## Navigation chrome` (which sections hide the header, tab labels and icon concepts, modal routes) so the user applies it. A hand-built header row on a screen whose stack also shows a header gives two headers: design for one — the default root layout hides headers (`headerShown: false`), so in-content `TopAppBar` is the norm for apps born from `mapples create`.
+- Tab icons require an icon ASSET in Creator; an `Icon` element or a glyph name does nothing there. Note the icon concept per tab in `design.md`; keep tab labels short and distinct — never fake a tab bar from a row of buttons on the page.
+- Everything inside the content area (chips, pills, badges, breadcrumbs, in-content title rows) is a CONTENT-SIZED library element: never width 100% inside a row or a horizontal scroll; never a `Button` where a `Chip` is meant.
+
+Recipes:
+- Chip row: `ChipGroup` {options: [{label, value, iconName?}], value, variant "filter", scrollable true} — it scrolls full-bleed itself; single chips are `Chip` {label, variant "assist" | "suggestion"}.
+- Count badge: `IconButton` {iconName, badgeCount, accessibilityLabel} or `Avatar` {badgeCount}; a standalone `Badge` {count} elsewhere. Digits only ("99+" past the max); no badge at zero.
+- Status pill (tags, "New", "Ready"): `Badge` {label, variant "text", tone} or `Chip` {variant "suggestion"}; at most two pills per row — never three lines of pills.
+- Breadcrumbs: `Breadcrumbs` {items: [{label, value}], separator "chevron", maxItems 4}; the last item is the current page. Never as the screen's only title.
+- In-content title row (only when the stack header is hidden): `TopAppBar` {title, showBack true, actions: [{iconName, value}], variant "small"}; the root keeps its safe-area `paddingTop` (≥ 48).
+- In-content tabs inside ONE screen: `Tabs` {items: [{label, value}], value} with each panel shown for one value (bind `$data={{ _visible: … }}` only when the project has the variable; otherwise design the first panel); a `BottomNavigationBar` is only for a single-page demo of a tab shell — real tabs are a tabs navigator (a `(group)/` with a `<Tabs />` layout).
+
+Pitfalls: chips built from Pressables; a badge drawn from Views; breadcrumbs typeset as a Headline; a header built twice (TopAppBar + stack header); `Tabs` or `BottomNavigationBar` used instead of a navigator.
+
+> Not ported (Creator-only): `set_navigator_options` / `set_route_options` and the `ref(theme:…)` / `ref(icon:…)` value syntax.

package/templates/claude/skills/mapples-design/reference/playbooks/onboarding-flow.md

@@ -0,0 +1,15 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Onboarding flow
+
+Welcome/intro flows: 2–3 value-prop screens with hero, dots and CTA arc.
+
+Value first: each screen sells ONE benefit from the brief — never a feature tour of the whole app. 2–3 screens maximum; every extra screen loses users.
+
+Structure per screen (root column, `justifyContent: 'space-between'`, screen padding 20–24, `paddingTop` ≥ 64, `paddingBottom` 32):
+1. Top bar: a right-aligned `TextLink` {label "Skip", tone "neutral", underline false} on every screen except the last.
+2. Hero block (`alignItems: 'center'`, gap 16): ONE hero — either a `GradientBackground` circle 96–120 holding an `Icon` glyph 44–56 (`styleSvg.color` a light hex), or an edge-to-edge photo band (`Image` with a picsum `source`, height 260–320, bottom-only corner radius 24). Then a centered Headline (≤ 5 words, the benefit, not the feature) and one Body line (≤ 2 lines, `theme.text.secondary`).
+3. Bottom block (gap 16, `alignItems: 'center'`): a `PageControl` {count, value, variant "bars"} — then the primary `Button` {variant "filled", size "lg", fullWidth true}.
+
+CTA copy arc: "Continue" on middle screens; the LAST screen carries the real ask — "Get started" primary plus a `TextLink` "Sign in" row underneath for returning users.
+
+Pitfalls: no emoji heroes; one hero per screen, never hero + photo; dots and button positions must not shift between screens (same bottom block on all three); wire screen→screen and last screen→auth or home in the wiring phase (`$actions` navigate + `router.push`).

package/templates/claude/skills/mapples-design/reference/playbooks/screen-flow-wiring.md

@@ -0,0 +1,37 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Screen flow wiring
+
+Wiring flows: every CTA connected, entries set, a walkable prototype.
+
+A project becomes a product when every path is walkable. After the screens exist, wire them — this is as much the design as the pixels.
+
+How a connection is written (both halves, on the element's primary event):
+
+```tsx
+import { router } from 'expo-router';
+// …
+<Button
+  label="Add to order"
+  variant="filled"
+  size="lg"
+  fullWidth
+  onPress={() => router.push('/(main)/cart')}
+  $actions={{ onPress: { type: 'mapples:navigate', staticData: { pageUuid: '<uuid>' } } }}
+/>
+```
+
+`$actions` is the Creator connection (the storyboard arrow); `onPress` is the runtime handler. The `pageUuid` is the `uuid` field of `.mapples/base/pages/<pageId>.json`, where `<pageId>` is the key in `.mapples/pages.json` whose `file` is the target route file. Rows use `ListItem`'s `onPress`, cards `MediaCard`'s / `Card`'s `onPress`.
+
+The contract:
+- Every PRIMARY `Button` navigates to a real page: onboarding Continue → next screen, Get started → auth or home, list row / card → its detail, detail CTA → the flow it starts (cart, booking, player). No dead primary buttons, ever.
+- Secondary paths too: Skip → where Continue ultimately lands; Sign in ↔ Create account cross-links; back is implied by the stack — never draw a back button into the tree (the shell provides it).
+- Every screen is REACHABLE: if nothing navigates to a screen in the plan, either wire the entry that was missed or question why the screen exists.
+- Every flow has an EXIT: the last onboarding screen leaves onboarding; a completed form lands somewhere meaningful (a success state or the content it created), not back at the empty form.
+- Entries: the app must open on the value, not on a settings screen. The initial section/route is a navigator option set in Creator — state the intended entry in `design.md` under `## Navigation chrome` (the scaffold's `index.tsx` of the initial section is the natural default).
+- Presentation: multi-screen interruptions and create-flows present as modal ROUTES (a navigator option — describe them in `design.md`); browsing pushes. Confirmations, pickers and quick details stay on the screen as `Dialog` / `BottomSheet` / `ActionSheet` with `visible={false}`, or bound through `$data={{ visible: { key: 'vars.<name>', active: true } }}` when the project has the variable — an overlay nobody can open or close is a dead end.
+
+Verify like a user: after wiring, walk the golden path mentally from the entry screen — first open → core value → primary action → done. Name the connection chain; every hop must exist. Then `mapples sync --yes --json` and check that `pushedOps` covers every `$actions` you added (an action on an element without a `$sid` yet lands on the sync after the element is tagged).
+
+Pitfalls: wiring only the happy screen and leaving detail pages orphaned; two buttons navigating to the same place with different labels; a tab bar plus in-content navigation to the same sections.
+
+> Not ported (Creator-only): `set_initial_route`, `set_entry_page`, `set_route_presentation`, `layout_storyboard`, `add_connection {action: {kind: "setState"}}` variable creation.

package/templates/claude/skills/mapples-design/reference/playbooks/settings-profile.md

@@ -0,0 +1,16 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Settings and profile
+
+Settings and profile screens: grouped cards, icon rows, switches, sign out.
+
+Root: vertical `ScrollView`, `contentContainerStyle` {gap: 24, padding: 20, paddingBottom: 40}.
+
+Profile header (when the app has accounts): centered column gap 8 — `Avatar` {size "xl", source a picsum "portrait" seed, or name for initials}, name Subtitle, email/handle Caption in `theme.text.secondary`. A `TextLink` "Edit profile" or `Button` {variant "outlined", size "sm"} under it.
+
+Groups: one `List` {variant "inset", header "PREFERENCES" | "ACCOUNT" | "ABOUT"} per group — the List draws the surface and the dividers (no gaps between rows — the list is the unit).
+
+Row anatomy: `ListItem` {leadingIconName, title, subtitle only for rows that need explanation, trailing "switch" for toggles, trailing "chevron" for navigation rows, trailing "text" + trailingText ("English") for pickers}. Keep one icon tint system across the groups.
+
+The destructive row: "Sign out" / "Delete account" as a `ListItem` {tone "error"} in its own last `List` — never mixed into a normal group.
+
+Pitfalls: no more than 5–6 rows per list; switches bind to real variables only when the project has them (`$data`), otherwise leave them unwired rather than faking state; app version as a final centered Caption is a nice close.

package/templates/claude/skills/mapples-design/reference/playbooks/stats-and-progress.md

@@ -0,0 +1,17 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Stats and progress
+
+Numbers, balances, goals: stat cards, progress bars, streaks — no fake charts.
+
+Numbers are the hero — let one big value carry each block.
+
+The hero number: a `StatTile` {label "BONUS BALANCE", value "1,240", unit "pts", caption, trend, trendValue, iconName, variant "elevated"} — or, for a brand-coloured hero, a `Card` with a deep brand-hex fill holding an Overline label and a Headline-sized value (fontSize 40–56 via a `styleTypography` override) with its unit in a Subtitle beside it (`flexDirection: 'row'`, `alignItems: 'flex-end'`, gap 8).
+- CONTRAST RULE: on a dark/brand fill, text is white/near-white hexes; on a light card, `theme.text` tokens. Never white text on a light background — if a gradient supplies the dark fill, the SAME node needs a solid dark `backgroundColor` fallback.
+
+Progress: `ProgressBar` {value, max, showLabel} for goals and uploads, `ProgressCircle` {value, size 72, showLabel} for rings. Under it one Caption: how far to the goal ("30 to go for a free coffee").
+
+Stat rows/grid: 2–3 `StatTile` in a row (`flexDirection: 'row'`, gap 12, each flex 1). Streaks: a row of 7 day-dots (24 circles — filled `theme.primary.main` for done, tinted for not, an `Icon` "checkmark" glyph 12 inside filled ones).
+
+Simple comparisons only: horizontal bar rows (Label + track/fill pair per row). Do NOT fake line/pie charts out of Views — if the product truly needs charts, say so instead of drawing a lie.
+
+Pitfalls: multiple hero numbers competing on one screen (pick one, demote the rest to the row/grid); percent fills must come from the actual data in the copy; progress color and CTA color should match so the goal reads as reachable.

package/templates/claude/skills/mapples-design/reference/playbooks/visual-hierarchy.md

@@ -0,0 +1,18 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Visual hierarchy
+
+Cross-screen craft: one focal point, the type ladder, grouping, squint-test review.
+
+A screen reads in ONE glance-order: focal point → supporting context → actions. Design that order deliberately; never let it emerge by accident.
+
+The focal point: exactly one per screen — the Headline, the hero photo, or the big number. Everything else steps down. Two elements fighting for attention (two Headlines, a hero photo AND a huge stat) is the most common failure: pick one, demote the other a full ladder step.
+
+The type ladder is strict: Headline (page title / hero claim, once) → Subtitle (section titles) → Body (reading text) → Label (row titles, buttons) → Caption (meta, secondary) → Overline (section eyebrows, uppercase). Never skip sideways — a section title is always Subtitle, a row title always Label, on every screen of the app. Emphasis inside a level comes from color (`theme.text.primary` vs secondary vs tertiary), not from inventing new sizes.
+
+Grouping is proximity before boxes: related items sit close (gap 4–8), groups separate wide (24–32). Reach for a card or divider only when spacing alone cannot carry the grouping. Within a group, align to ONE left edge; icon centers align to the text they accompany.
+
+Weight discipline: at most two font weights visible per screen region. Color accents (`theme.primary.main`) mark interactive or key items ONLY — an accent on decoration teaches users to ignore it.
+
+The squint test (run it on every re-read of a finished file): blur your eyes at the screen as the phone would draw it. You should still see WHERE to look first and WHAT is tappable. If everything blurs into even gray noise, the hierarchy is flat — raise the focal point, quiet the rest. If one block screams that is not the primary action, swap emphasis.
+
+Pitfalls: three or more text sizes inside one card; every row shouting in bold; accents on more than ~10 percent of the screen; centered text mixed with left-aligned text in the same block.

package/templates/claude/skills/mapples-design/reference/style-guides.md

@@ -0,0 +1,92 @@
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# Style guides (phase 1)
+
+Ported from the Creator's design setup (`service--mapples-ai` `design/generate.ts`): first art
+directions, then one compact style guide per direction. The user picks one; the full token set
+(phase 2) realizes exactly that guide.
+
+## 1. Art directions
+
+Act as a creative director choosing art directions for this mobile app's design system.
+
+Propose exactly **3** art directions FOR THIS PRODUCT — grounded in its domain, audience and
+mood, never a generic template menu. Make them genuinely different from each other: vary palette
+temperature, typography class (serif / geometric sans / humanist sans / rounded / mono accents),
+shape language (sharp ↔ pill), and density (airy ↔ compact). Each direction: a short evocative
+name (2–40 chars, e.g. "Neon Court") and one tight clause (≤ 25 words) of concrete visual moves:
+palette temperature, typography class, shape language, density.
+
+## 2. Style guide per direction
+
+Act as a senior product designer sketching a compact style guide for this mobile app, for ONE
+direction at a time. Make it unmistakably different from the other directions and from a
+default blue Material palette.
+
+Rules:
+
+- Colors are hex. The preview maps are BOTH light and dark; dark is a real dark design (dark
+  surfaces, lighter text), not an inversion. `text` must have ≥ 4.5:1 contrast against
+  `background`; `onPrimary` against `primary` likewise.
+- Fonts come ONLY from the bundled library (family + weight). Pick pairings that fit the
+  direction; body fonts must be sans or a highly legible serif.
+- `iconFamily` comes ONLY from the icon library. Pick the pack whose stroke weight and shape
+  language match the direction (thin strokes for airy directions, solid glyphs for bold ones).
+- `instructions` are the seed for the FULL design system generated later: palette logic,
+  typography roles, shape language (including the elevation language — soft shadows vs flat
+  borders/contrasting surfaces, with flat a first-class choice — and radius feel), spacing feel,
+  component character, one explicit don't. Concrete, 60–100 words, no marketing language.
+
+Shape of one guide (write it into `design.md` when chosen):
+
+```md
+### <Name> — <direction in a few words>
+Rationale: <one sentence why it fits the product>
+Preview light: background #… card #… text #… textMuted #… primary #… onPrimary #… accent #…
+Preview dark:  background #… card #… text #… textMuted #… primary #… onPrimary #… accent #…
+Radius: <0–32>  ·  Fonts: headline <Family Weight> / body <Family Weight> / button <Family Weight>
+Icon family: <key>
+Instructions: <60–100 words>
+```
+
+## Font library
+
+`"<Family>-<Weight>"` is the registered React Native family name (`Manrope-SemiBold`). Weights:
+Regular, Medium, SemiBold, Bold unless noted.
+
+| Family | Category | Character | Pairs with |
+| --- | --- | --- | --- |
+| Inter | sans | neutral, highly legible UI sans | Playfair Display, Fraunces, IBM Plex Mono |
+| Manrope | sans | modern geometric, friendly tech | Fraunces, Inter, IBM Plex Mono |
+| DM Sans (`DMSans`) | sans | low-contrast geometric, calm product UI | Playfair Display, Fraunces |
+| Plus Jakarta Sans (`PlusJakartaSans`) | sans | rounded geometric, startup/fintech | Inter, Fraunces |
+| Poppins | sans | round geometric, playful consumer apps | Nunito, Inter |
+| Nunito | sans | soft rounded terminals, approachable | Poppins, Outfit |
+| Space Grotesk (`SpaceGrotesk`) | sans | quirky technical grotesk, dev tools | Inter, IBM Plex Mono |
+| Sora | sans | wide geometric display sans, bold headlines | Inter, DM Sans |
+| Outfit | sans | clean geometric display, fashion/lifestyle | DM Sans, Nunito |
+| Playfair Display (`PlayfairDisplay`) | serif — Regular/SemiBold/Bold | high-contrast editorial serif for headlines | Inter, DM Sans |
+| Fraunces | serif — Regular/SemiBold/Bold | soft wonky serif, warm and characterful | Manrope, Inter, DM Sans |
+| IBM Plex Mono (`IBMPlexMono`) | mono — Regular/Medium | monospace for code, data and labels | Inter, Space Grotesk |
+
+## Icon library
+
+| Key | Character |
+| --- | --- |
+| ionicons | iOS-flavored rounded glyphs with filled and -outline pairs; safe modern default |
+| material-icons | Google Material: solid, geometric, compact |
+| material-design-icons | community Material superset; huge coverage, filled and outline variants |
+| feather | thin 2px stroke outlines; minimal and airy |
+| lucide | Feather's successor; consistent strokes, wide coverage |
+| ant-design | clean enterprise outlines; restrained and precise |
+| entypo | thick rounded solid glyphs; friendly and bold |
+| octicons | GitHub's set; crisp outlines tuned for small sizes |
+| fontawesome5-solid | Font Awesome 5 solid: heavy filled, classic |
+| fontawesome6-solid | Font Awesome 6 solid: heavy filled, modern |
+| simple-line-icons | ultra-light elegant line icons |
+
+The icon family is a project setting in Creator; from code, `Icon iconName="…"` uses the glyph
+names of that family (ionicons names like `home-outline`, `search`, `chevron-forward` when in
+doubt). An unknown name renders as a broken glyph — prefer a common name over a guessed one.
+
+> Not ported (Creator-only): the streaming preview cards, the `repairViolations` pass and the
+> four-guide generation count (three here, so the table fits a chat reply).

package/templates/claude/skills/mapples-sync/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: mapples-sync
+description: Running `mapples sync` from an agent — the --yes --json invocation, the JSON report fields, exit codes 0/1/2/3/4, and what to do on conflicts, deprecated files, NON_LITERAL_PROP warnings, read-scoped keys and offline runs. Use before and after every sync in a Mapples-linked app.
+---
+<!-- GENERATED by Mapples __CLI_VERSION__ — re-run mapples agent install --force to refresh -->
+# mapples sync
+
+`mapples sync` is the only way changes reach Creator. Run it from the app root as
+
+```bash
+mapples sync --yes --json
+```
+
+- `--yes` accepts every adoption proposal (new route files, pages, components) without a prompt —
+  required, because you have no TTY. Add `--no-adopt` to push edits to managed files only and
+  leave new files untouched (e.g. a helper you do not want on the canvas yet).
+- `--json` prints one JSON report and nothing else. Always parse it; never rely on the exit
+  code alone.
+- The CLI is on the app's `devDependencies`; use `npx mapples …` (or `yarn mapples …`) when the
+  bare command is not on the PATH.
+
+## What one run does
+
+1. Adopts new files (`--yes`): react-native primitives become `@mapples/ui` elements with
+   `styled` props; a new file under the routes dir joins the navigator of its directory (a new
+   `(group)/` with a generated-header `_layout.tsx` becomes its own navigator).
+2. Extracts every managed file; elements without `$sid` are tagged and the file is rewritten.
+3. Pulls Creator's changes since the last sync, 3-way merges per element and prop, writes remote
+   changes into your files surgically.
+4. Pushes your edits as JPATCH transactions (retrying on 409), updates `.mapples/head`,
+   `pages.json`, `components.json`, `base/`.
+
+## The report
+
+```json
+{
+  "pulledOps": 0, "pushedOps": 42, "head": "b3:…", "offline": false, "exitCode": 0,
+  "files": [{ "file": "app/index.tsx", "action": "updated", "detail": "tagged 12 new element(s)" }],
+  "conflicts": [{ "file": "app/index.tsx", "sid": "nd_…", "reason": "same-prop", "props": ["text"], "deprecatedTo": "app/_depr_20260916120000_index.tsx.old", "detail": "…" }],
+  "warnings": [{ "file": "app/index.tsx", "kind": "NON_LITERAL_PROP", "sid": "nd_…", "prop": "text", "detail": "…" }],
+  "dropped": [{ "index": 3, "id": "nd_…", "reason": "…", "op": { "op": "update", "entity": "RenderNode" } }],
+  "serverWarnings": ["CHILDREN_REBASED …"],
+  "notes": ["navigation: app/(main)/ had no navigator — created tabs navigator “Main” on “Root” (kind read from its _layout.tsx)"]
+}
+```
+
+| Field | Read it as |
+| --- | --- |
+| `files[].action` | `created` / `updated` / `regenerated` (from Creator after a conflict) / `deprecated` (your version moved to `_depr_…`) |
+| `conflicts[]` | both sides changed the same prop or one deleted what the other edited — the file was deprecated and regenerated |
+| `warnings[]` | lossy steps: `NON_LITERAL_PROP` (an expression prop stays code-only), `UNKNOWN_ELEMENT_WITH_SID`, … |
+| `dropped[]` | ops the server skipped (target gone) — the change did not land |
+| `serverWarnings[]` | e.g. `CHILDREN_REBASED`: the server reordered children after a concurrent edit |
+| `offline` | true = nothing reached the server; ops parked in `.mapples/outbox/` and drained next run |
+| `notes[]` | navigator creation, agent-lease heartbeat misses, rebases |
+
+## Exit codes
+
+| Code | Meaning | Do |
+| --- | --- | --- |
+| 0 | synced | read `pushedOps`, `files`, `warnings` |
+| 1 | error (bad key, malformed file, server refusal) | read stderr; fix the cause; never retry blindly |
+| 2 | synced **with conflicts** | for every `conflicts[]` entry: diff `deprecatedTo` against the regenerated file, re-apply your intent onto the new file, sync again |
+| 3 | agent lease gone (from `mapples agent …`) | stop working, tell the user Creator disconnected the agent |
+| 4 | project busy (from `mapples agent start`) | another agent session holds the project — ask before `--takeover` |
+
+## After a sync
+
+- **Re-read every file the report lists** before editing it again — `$sid`s were added, Creator's
+  edits were written in, the marker may have moved.
+- `NON_LITERAL_PROP` on something you meant to be a literal: replace the expression with the
+  literal value (`text={title}` → `text="Today"`), sync again.
+- A `deprecated` file with no conflict entry means the CLI had to own that position (a layout
+  you wrote without the generated header): let the generated file stand.
+- `pushedOps: 0` after you changed a managed file means the extraction saw nothing: check that
+  the elements are Mapples imports with literal props, and that the file has no syntax error
+  (the report lists `SYNTAX_ERROR` warnings).
+- `offline: true`: run again once online; do not edit `.mapples/outbox/`.
+
+## Errors you may see
+
+- `push rejected: API key is read-scoped …` — the `MAPPLES_SECRET` / `.mapples/secret` key can
+  only read. Ask the user for a read & write key (Creator → Project → Settings → API keys) and
+  to restart with `MAPPLES_SECRET=<key> claude`; do not edit `.mapples/secret` yourself.
+- `no .mapples/config.json` — you are not in the app root, or the app is not linked; do not run
+  `mapples init` on your own — ask.
+- `HEAD_MISMATCH … could not be committed after 5 rebases` — Creator is being edited at the same
+  time; wait a moment and sync again.
+
+Never delete `.mapples/head`, `.mapples/base/`, `.mapples/pages.json` or `.mapples/components.json`
+to "fix" a sync — that discards the merge base and turns the next run into a cold bootstrap that
+can deprecate every file.

package/templates/gitignore

@@ -7,3 +7,5 @@ web-build/
 .mapples/outbox/
 # project API secret — never commit
 .mapples/secret
+# agent-session lease state — local only
+.mapples/agent.json

package/templates/package.json

@@ -11,6 +11,7 @@
   },
   "dependencies": {
     "@mapples/action": "^1.1.2",
+    "@mapples/components": "^1.2.1",
     "@mapples/form": "^1.2.0",
     "@mapples/inlang": "^1.2.0",
     "@mapples/render": "^1.2.0",