agentera 3.0.0-dev.2 → 3.0.0-dev.21

package/bundle/DESIGN.md

@@ -0,0 +1,233 @@
+# Agentera
+
+Visual identity system for Agentera. Terminal-native tokens for CLI and agent-rendered Markdown; mobile UI tokens live in [`packages/mobile/DESIGN.md`](./packages/mobile/DESIGN.md).
+
+## Surface register
+
+One brand (Agentera), three register layers: terminal/mobile surfaces (below), brand-vs-product output registers, and suite-vs-project design authorities.
+
+| Surface | Authority | Renders |
+| --- | --- | --- |
+| `terminal` | This file (`DESIGN.md`) | CLI dashboard, capability introductions, structured artifact headers in Markdown |
+| `mobile` | `packages/mobile/DESIGN.md` | Touch UI, smart bar, sidebar, chat composer, responsive layouts |
+
+Shared across surfaces: product name, capability glyphs, sharp-colleague voice.
+Not shared: box-drawing logo usage (terminal key moments only), terminal severity arrows in mobile UI, Tailwind touch targets in terminal output.
+
+## Output Registers
+
+Agentera separates **where** tokens apply. One `DESIGN.md` holds both registers; agents must know which register governs the surface they render.
+
+### Brand register
+
+Human-facing root documentation: `README`, `UPGRADE`, `CHANGELOG`, package and plugin copy, and other public prose for installers and contributors. Voice may be warmer and more explanatory. The logo may appear in README hero contexts. Skill glyphs are optional; prefer plain capability names in prose.
+
+### Product register
+
+Agent-rendered terminal output for whichever design authority this file belongs to:
+
+- **Suite `DESIGN.md`:** status dashboard, capability introductions and exits, Agentera CLI-formatted state summaries
+- **Project `DESIGN.md`:** the host product's own CLI, agent, or terminal-native output
+
+The product register enforces logo scarcity, protocol glyphs, section dividers, and composition rules below. When an agent emits structured terminal Markdown on behalf of Agentera, the **suite** product register wins even if the same session also edited README or the host project has its own `DESIGN.md`.
+
+### Design authorities (suite vs project)
+
+Agentera maintains **two design authorities**. They never merge into one artifact.
+
+#### Suite design authority
+
+Governs **Agentera capability chrome** when the suite renders terminal output inside any host project.
+
+| Source | Role |
+|--------|------|
+| `protocol.yaml` | Shared glyphs, dividers, severity, confidence, and exit tokens (npm bundle or app-home skills) |
+| `agentera prime --context` capability prose (D65) | Status dashboard, introductions, exits, and startup contracts |
+| v2 `$AGENTERA_HOME/app/DESIGN.md` when present | Legacy managed-install suite product register |
+| Agentera repo root `DESIGN.md` | Suite dogfood terminal register plus brand register for this repository |
+
+**Surfaces:** status orientation dashboard, capability introductions and exit markers, CLI-formatted `agentera state` summaries agents emit as Agentera.
+
+#### Project design authority
+
+Governs the **host repository's own product** — web UI, the user's coding-agent CLI, docs site, or other app output the design capability was asked to design.
+
+| Source | Role |
+|--------|------|
+| Project `DESIGN.md` | Per-repo artifact via docs mapping (default: project root) |
+
+**Surfaces:** the project's application UI, the project's own CLI or agent terminal output, and project-specific styled docs. Not Agentera suite chrome.
+
+#### Resolution rules
+
+- v3 npm publish (`packages/cli/bundle/`) ships `skills/` and `protocol.yaml`; it does **not** copy suite `DESIGN.md` into host projects.
+- v2 managed app-home may include `app/DESIGN.md`; project install still does **not** copy it to the host project root.
+- Design in a host project writes **project** `DESIGN.md` only; never merge suite design sources into it.
+- Status reads project design for **status metadata** (exists, stale, missing) — not to style suite chrome.
+- When both authorities apply in one session, suite chrome follows suite sources; the host product follows project `DESIGN.md`.
+- In the Agentera repository, root `DESIGN.md` is suite terminal dogfood plus brand register; `packages/mobile/DESIGN.md` is the mobile surface register.
+
+## Philosophy
+
+The ambitious workshop. Every visual element carries semantic weight; craft and density are the same move. Open structure over enclosure: no frames except the logo, breathing room between sections, precision in alignment. The box-drawing logo is the crown; everything else earns distinction through Unicode glyphs and whitespace.
+
+Modern terminal assumed. Full Unicode space available.
+
+## Logo
+
+The agentera logo uses box-drawing characters exclusively. It appears at key moments only: the status dashboard, major completions, significant artifacts. Scarcity keeps it special.
+
+<!-- design:logo -->
+
+```yaml
+text: |
+  ┌─┐┌─┐┌─┐┌┐┌┌┬┐┌─┐┬─┐┌─┐
+  ├─┤│ ┬├┤ │││ │ ├┤ ├┬┘├─┤
+  ┴ ┴└─┘└─┘┘└┘ ┴ └─┘┴└─┴ ┴
+placement: standalone-top
+usage: key-moments-only
+```
+
+## Skill Glyphs
+
+Each skill has a unique Unicode glyph that appears in section headers as a subtle signature. The glyphs lean into geometric shapes: angular, precise, echoing the logo's sharp corners.
+
+<!-- design:glyphs -->
+
+```yaml
+status:      { glyph: "⌂", code: "U+2302", meaning: "home base" }
+build:       { glyph: "⧉", code: "U+29C9", meaning: "joined building blocks" }
+audit:       { glyph: "⛶", code: "U+26F6", meaning: "viewfinder frame" }
+discuss:     { glyph: "❈", code: "U+2748", meaning: "spark of insight" }
+plan:        { glyph: "≡", code: "U+2261", meaning: "structured layers" }
+vision:      { glyph: "⛥", code: "U+26E5", meaning: "guiding star" }
+optimize:    { glyph: "⎘", code: "U+2398", meaning: "measurement" }
+document:    { glyph: "▤", code: "U+25A4", meaning: "text on page" }
+profile:     { glyph: "♾", code: "U+267E", meaning: "permanent mark" }
+research:    { glyph: "⬚", code: "U+2B1A", meaning: "frame to fill" }
+design:      { glyph: "◰", code: "U+25F0", meaning: "design grid" }
+orchestrate: { glyph: "⎈", code: "U+2388", meaning: "helm, steering" }
+```
+
+## Status Tokens
+
+Task and item completion states. Square family: fill progression from empty to solid.
+
+<!-- design:status -->
+
+```yaml
+complete:    { glyph: "■", code: "U+25A0" }
+in-progress: { glyph: "▣", code: "U+25A3" }
+open:        { glyph: "□", code: "U+25A1" }
+blocked:     { glyph: "▨", code: "U+25A8" }
+```
+
+## Severity Tokens
+
+Issue urgency. Rightward arrows: more arrows, more serious.
+
+<!-- design:severity -->
+
+```yaml
+critical: { glyph: "⇶", code: "U+21F6", weight: 3 }
+degraded: { glyph: "⇉", code: "U+21C9", weight: 2 }
+annoying: { glyph: "⇢", code: "U+21E2", weight: 1 }
+```
+
+## Confidence Tokens
+
+Decision certainty. Box-drawing line weight: heavier line, firmer commitment.
+
+<!-- design:confidence -->
+
+```yaml
+firm:        { glyph: "━", code: "U+2501" }
+provisional: { glyph: "─", code: "U+2500" }
+exploratory: { glyph: "┄", code: "U+2504" }
+```
+
+## Trend Tokens
+
+Direction of change.
+
+<!-- design:trends -->
+
+```yaml
+improving: { glyph: "⮉", code: "U+2B89" }
+degrading: { glyph: "⮋", code: "U+2B8B" }
+```
+
+## Structural Tokens
+
+Layout primitives shared across all skills and artifacts.
+
+<!-- design:structure -->
+
+```yaml
+section-divider: "─── label ───────"
+list-item:       { glyph: "▸", code: "U+25B8" }
+separator:       { glyph: "·", code: "U+00B7" }
+flow:            { glyph: "→", code: "U+2192" }
+progress-bar:    "█▓░"
+```
+
+## Composition Rules
+
+<!-- design:constraints -->
+
+```yaml
+structural:
+  - pattern: outer-frames
+    rule: prohibited
+    reason: "Open structure — no enclosure except the logo"
+    exception: "Logo box-drawing characters only"
+  - pattern: glyph-in-section-headers
+    rule: prohibited
+    reason: "Section headers are clean labels"
+  - pattern: logo-on-every-invocation
+    rule: prohibited
+    reason: "Logo at key moments only — scarcity keeps it special"
+
+compositional:
+  - pattern: skill-introduction
+    rule: required
+    format: "─── glyph skillname · context ───"
+  - pattern: breathing-room
+    rule: required
+    format: "Blank lines between sections"
+  - pattern: narrative-position
+    rule: convention
+    format: "Narrative summaries close sections, not open them"
+  - pattern: markdown-layering
+    rule: required
+    reason: "All artifacts stay valid Markdown — visual tokens layer within sections"
+
+agent-output:
+  - pattern: emoji-status-icons
+    rule: prohibited
+    reason: "Use severity and status tokens from this file, not emoji"
+  - pattern: markdown-tables-in-agent-dashboard
+    rule: prohibited
+    scope: [status-dashboard, capability-intros]
+    reason: "Prefer dividers and metric lines over generic table slop"
+  - pattern: bold-decoration-spam
+    rule: prohibited
+    reason: "Emphasis sparingly; structure carries meaning in the product register"
+  - pattern: unicode-box-frames
+    rule: prohibited
+    exception: logo
+    reason: "No outer frames except the logo box-drawing characters"
+  - pattern: invented-glyphs
+    rule: prohibited
+    reason: "Use declared skill, status, and severity tokens only"
+
+slop-test:
+  description: "Generic agent formatting fails the product register"
+  fail-signals:
+    - "Swap the project name and nothing distinctive remains"
+    - "Emoji, sparkles, or checkmark bullets replace declared tokens"
+    - "Section headers ignore product-register dividers or glyph discipline"
+    - "Logo or heavy framing on routine status updates"
+  pass: "A reader identifies Agentera terminal output without seeing the project name"
+
+```

package/bundle/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/bundle/README.md

@@ -0,0 +1,158 @@
+<div align="center">
+<pre>
+┌─┐┌─┐┌─┐┌┐┌┌┬┐┌─┐┬─┐┌─┐
+├─┤│ ┬├┤ │││ │ ├┤ ├┬┘├─┤
+┴ ┴└─┘└─┘┘└┘ ┴ └─┘┴└─┴ ┴
+</pre>
+
+<strong>One agent, one CLI, many capabilities.</strong>
+</div>
+
+Agentera is a project-memory and workflow layer for coding agents. It keeps
+direction, plans, decisions, progress, documentation state, and health evidence
+in the repository so work can continue across sessions and runtimes.
+
+## Get started
+
+Agentera 3.0 is the self-contained TypeScript package on npm. Before the stable
+dist-tag promotion, use `@next`; after promotion, the same commands work with
+`agentera@latest` or an installed `agentera` binary.
+
+```bash
+npx -y agentera@next prime
+```
+
+Run that from a git project. In an editor runtime, invoke `/agentera`
+(`$agentera` in Codex) for the rendered status dashboard.
+
+`prime` is deliberately bounded: it summarizes current project state and the
+next useful action. Use `doctor` when you need detailed install and runtime
+evidence.
+
+```bash
+npx -y agentera@next prime --format json
+npx -y agentera@next doctor --format json
+```
+
+## Supported runtimes
+
+Agentera 3.0 has exactly four active runtime identities:
+
+- OpenCode
+- Codex
+- Cursor
+- GitHub Copilot
+
+Cursor Agent CLI is the required Cursor surface and Cursor IDE is conditional;
+both belong to the single `cursor` runtime identity. The canonical portable
+skill is `~/.agents/skills/agentera`.
+
+On the v3 development channel, a dry-run without a selector previews lifecycle
+findings for all active runtimes without making changes. Approve Agentera-owned
+runtime operations separately:
+
+```bash
+npx -y agentera@next upgrade --runtime all --dry-run
+npx -y agentera@next upgrade --runtime all --yes
+```
+
+You can replace `all` with `opencode`, `codex`, `cursor`, or `copilot`.
+Preview creates no files, directories, locks, caches, telemetry, or state
+changes. Apply writes only declared Agentera-owned resources. Native package
+installation, authentication, enablement, and trust remain user-owned and are
+reported as `action_required`.
+
+Secure automatic lifecycle apply currently requires Linux `/proc/self/fd`.
+Other platforms still receive the complete preview and explicit manual actions,
+but filesystem operations remain `action_required`.
+
+`prime`, status, and project-integration output summarize the same lifecycle
+snapshot, including runtime counts, blockers, and the recommended next action.
+
+Claude Code is retired from active support. Its only lifecycle command is a
+separate, explicit cleanup of the exact Agentera-owned legacy skill link:
+
+```bash
+npx -y agentera@next upgrade --legacy-cleanup claude --dry-run
+npx -y agentera@next upgrade --legacy-cleanup claude --yes
+```
+
+Historical Claude transcripts are excluded by default. A local import requires
+explicit `--import-source claude` consent, records historical provenance, and
+does not create an active runtime identity.
+
+## Project state
+
+Agentera resolves artifact paths through the CLI and `.agentera/docs.yaml`.
+Normal reads use `agentera state`; supported writes use the typed writer.
+
+```bash
+agentera state todo
+agentera state plan
+agentera state query --list-artifacts
+agentera state progress explain --verb append --format json
+```
+
+Bounded collection retrieval uses stable identities, opaque snapshot cursors,
+explicit omissions, and exact detail commands. The runtime contract is
+[`references/artifacts/state-storage-authority.yaml`](./references/artifacts/state-storage-authority.yaml).
+
+```bash
+agentera state plan list --format json
+agentera state plan get --plan PLAN_ID --format json
+agentera state plan tasks list --limit 20 --format json
+agentera state experiments list --objective OBJECTIVE_ID --format json
+agentera state experiments get --objective OBJECTIVE_ID --number N --format json
+```
+
+Plan list/get spans the active plan and immutable plan archives. Plan task
+list/get is active-plan-only. Experiment retrieval merges its bounded projection
+with objective-owned immutable archives and reports detail as full, summary-only,
+or unavailable.
+
+The standard project state is:
+
+- `.agentera/vision.yaml` — product direction
+- `.agentera/plan.yaml` — active and archived plans
+- `.agentera/progress.yaml` — shipped work and verification
+- `.agentera/decisions.yaml` — durable reasoning
+- `.agentera/health.yaml` — architecture and project health
+- `.agentera/docs.yaml` — documentation inventory and path/version mappings
+- `TODO.md`, `CHANGELOG.md`, and `DESIGN.md` — human-facing project artifacts
+
+## Capabilities
+
+| | Capability | Use it when you need... |
+| --- | --- | --- |
+| ⌂ | status | Project briefing and next best action |
+| ⛥ | vision | Product direction |
+| ❈ | discuss | Structured deliberation |
+| ⬚ | research | External pattern analysis |
+| ≡ | plan | Scoped plan with acceptance criteria |
+| ⧉ | build | One verified development cycle |
+| ⎘ | optimize | Metric-driven optimization |
+| ▤ | document | Documentation aligned with code |
+| ◰ | design | Visual identity and design tokens |
+| ⛶ | audit | Architecture and project health audits |
+| ♾ | profile | Reusable decision profile |
+| ⎈ | orchestrate | Autonomous plan execution with evaluation |
+
+## Monorepo
+
+| Package | Role |
+| --- | --- |
+| `packages/cli` (`agentera`) | Primary TypeScript CLI and bundled runtime data |
+| `packages/web` (`@agentera/web`) | Marketing and Starlight documentation site |
+| `packages/mobile` (`@agentera/mobile`) | Docs-only mobile product stub |
+
+Contributor commands and repository rules live in [AGENTS.md](./AGENTS.md).
+Migration and recovery details live in [UPGRADE.md](./UPGRADE.md).
+
+```bash
+pnpm -C packages/cli test
+pnpm -C packages/cli run typecheck
+pnpm -C packages/cli build
+vp run web:check
+```
+
+License: [Apache-2.0](./LICENSE) · Author: Jonathan Gabor