dreamteamer 0.6.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2026 Gilad Khen
+
+   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/NOTICE

@@ -0,0 +1,16 @@
+dreamteamer
+Copyright 2026 Gilad Khen
+
+This product includes software developed by Gilad Khen.
+
+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/README.md

@@ -0,0 +1,83 @@
+# dreamteamer
+
+A workspace compiler for coding agents. Module sources compile **explicitly** into `.dreamteamer/`,
+the single runtime read surface, and from there into per-harness adapters — Claude Code, Codex, Pi,
+Gemini CLI, Cursor. Data is plain files: records are `<id>.<suffix>.<ext>`, ids are paths,
+references are `<collection>/<id>`. A write lands on disk; `dreamteamer commit` publishes it, one
+commit per repo. Hard validation before disk; nothing hidden.
+
+```bash
+npm i dreamteamer         # engine + the `dreamteamer` bin
+npx dreamteamer init      # scaffold a workspace
+npx dreamteamer compile   # sources → .dreamteamer (+ harness adapters)
+npx dreamteamer check     # validate every record
+npx dreamteamer help      # the full command surface
+```
+
+There is a VS Code extension — [dreamteamer-vscode](https://github.com/dreamteamer/dreamteamer-vscode) —
+which loads the engine **your workspace pins**, so the editor, the CLI and any agent session are
+provably running the same code.
+
+## Sources, and where they come from
+
+A module contributes collections, skills, agents, commands, command-bindings, UI views and
+collection templates. Modules are discovered over three channels, in precedence order: inline
+`modules/*`, then `git_modules/*`, then npm dependencies. Sources live **flat at a module root** —
+`modules/crm/skills/`, beside `package.json` — and an unknown folder at a module root is a compile
+error rather than a silent skip.
+
+## Attached repos (`repos`) vs modules (`git-modules`)
+
+Two different lifecycles, deliberately two different homes.
+
+**Modules** are declared in the workspace's `package.json` under `dreamteamer.git-modules` and
+restored by `dreamteamer install`. They MUST live in config rather than in records because of a
+genuine bootstrap ordering: a fresh clone has no `.dreamteamer`, therefore no compiled schemas,
+therefore no readable records — so module clones have to be restorable before anything can be read.
+
+**Attached repos** are `repos` records under `data/repos/`. They contribute NOTHING to the
+workspace — no schema, no skills, no UI. A repo record says only where a related git repo lives and
+how to get it, and exists so that domain collections can reference `repos/<id>` instead of each
+inventing its own url/ref/identity fields. Because they are not needed at compile time, they get to
+be data — which buys hard validation, the record CLI verbs, and history for free.
+
+Working trees are materialized **on demand**:
+
+```bash
+dreamteamer repos ensure <id>     # clone if missing, print the path; idempotent
+dreamteamer repos ensure --all    # explicit opt-in, e.g. before going offline
+```
+
+`install` deliberately does not do this. The record count only grows while the fraction any given
+session needs only shrinks, so eager restore would make every fresh clone slow, would require every
+identity's credentials to be present at install time, and would let one unreachable remote fail the
+whole install. Lazy materialization fails only the action you asked for, at the moment you asked.
+
+Path resolution is `<repos-path>/<identity>/<name>`, where `repos-path` is a `package.json`
+`dreamteamer` key defaulting to `projects`, and `identity` is optional (omit it for
+`<repos-path>/<name>`). A record's `path` field overrides the derivation entirely.
+
+**`identity` is an opaque path segment to the engine.** A workspace may use it to select a git
+identity — via `~/.gitconfig` `includeIf` rules keyed on the path, for example — but that resolution
+happens outside the engine, which only joins it into a path.
+
+**A missing working tree is not a violation.** `dreamteamer check` does not and must not flag it: a
+reference to `repos/<id>` resolves because the RECORD exists, and whether the clone is on disk is
+irrelevant to referential integrity. Presence is reported by `dreamteamer status`.
+
+## Domain modules are recipes, not packages
+
+Anything domain-shaped — people, meetings, products, content — belongs in a module, and a generic
+version belongs in a recipe a workspace **copies and adapts**. They are deliberately not installable
+packages: four workspaces wanted a CRM and all four wanted a different `contacts`, so an import
+would force one answer and make every divergence a fork.
+
+## Contributing
+
+Issues are welcome. For anything larger than a typo, please open a discussion before a pull request —
+this is a small, deliberately lean codebase (`npm run metrics` enforces size budgets), and it's
+better to agree on the shape first.
+
+## License
+
+Apache-2.0 © 2026 Gilad Khen. See [LICENSE](LICENSE).

package/agents/dreamteamer.agent.md

@@ -0,0 +1,7 @@
+---
+name: dreamteamer
+description: master agent — routes a request to the right collection, skill or agent; the default operator for data-facing work
+tools: [Read, Write, Edit, Grep, Glob, Bash]
+skills: [skills/using-dreamteamer]
+---
+classify the request (data op / schema op / authoring / capability discovery), load the matching skill, and execute or delegate. when a command dispatches you, load the skills that command names, do exactly what it asks, and report a concise summary of what you wrote — record ids, not prose.

package/bin/dreamteamer.js

@@ -0,0 +1,65 @@
+#!/usr/bin/env node
+// self-shadowing (decision 24, applied to the engine itself): when the workspace carries a
+// git_modules/dreamteamer working clone, THAT engine runs — same npm-link semantics module
+// content already gets. the npm-installed copy is bootstrap + fallback; the dev clone wins.
+import fs from 'node:fs';
+import path from 'node:path';
+import { pathToFileURL, fileURLToPath } from 'node:url';
+
+// path segments that mean "the thing below me is a module of the thing above me", never a
+// workspace. Declared up here, not beside findDevClone: that call sits at module top level, so a
+// `const` below it is still in its temporal dead zone when the walk needs it.
+const MODULE_SEGMENTS = new Set(['node_modules', 'git_modules', 'modules']);
+
+const self = fileURLToPath(import.meta.url);
+const devBin = findDevClone(process.cwd());
+// `realpath`, NOT `path.resolve`: resolve is pure string math and does not follow symlinks, so a
+// workspace whose git_modules/dreamteamer is a SYMLINK to the engine it is already running (the
+// normal shape for a dev clone, and a common shape under a repos folder) compared two spellings
+// of one file, decided they differed, and re-imported itself — a circular import that never
+// settles, so the process exited silently having done nothing at all. Worse than a crash: every
+// command "succeeded" with no output and no effect.
+if (devBin && realpath(devBin) !== realpath(self)) {
+	console.error(`… running the git_modules/dreamteamer dev clone (shadows the installed engine)`);
+	await import(pathToFileURL(devBin).href);
+} else {
+	const { run } = await import('../src/cli.js');
+	run(process.argv.slice(2));
+}
+
+/** Canonical on-disk identity of a path — symlinks followed, falling back to the literal path. */
+function realpath(p) {
+	try {
+		return fs.realpathSync(p);
+	} catch {
+		return path.resolve(p);
+	}
+}
+
+// same workspace rule as src/workspace.js (nearest package.json with a `dreamteamer` key, climbing
+// out only of module nesting), duplicated here because the dev clone must be found BEFORE choosing
+// which src/ to load. Keep the two in step — they must never disagree about which workspace this is.
+function findDevClone(start) {
+	let dir = path.resolve(start);
+	const candidates = []; // nearest → topmost
+	while (true) {
+		const p = path.join(dir, 'package.json');
+		if (fs.existsSync(p)) {
+			try {
+				if ('dreamteamer' in JSON.parse(fs.readFileSync(p, 'utf8'))) candidates.push(dir);
+			} catch { /* unparseable — keep walking */ }
+		}
+		const parent = path.dirname(dir);
+		if (parent === dir) break;
+		dir = parent;
+	}
+	if (!candidates.length) return null;
+	let workspace = candidates[0];
+	for (const higher of candidates.slice(1)) {
+		const viaModule = path.relative(higher, workspace).split(path.sep).some((seg) => MODULE_SEGMENTS.has(seg));
+		if (!viaModule) break;
+		workspace = higher;
+	}
+	const bin = path.join(workspace, 'git_modules', 'dreamteamer', 'bin', 'dreamteamer.js');
+	return fs.existsSync(bin) ? bin : null;
+}

package/collection-templates/docs.collection-template.yaml

@@ -0,0 +1,14 @@
+name: docs
+template:
+  storage: { codec: md, shape: file }
+  id:
+    generate: "{{ created | date }}--{{ title | slug }}"
+    pattern: "^\\d{4}-\\d{2}-\\d{2}--[a-z0-9-]+$"
+  schema:
+    type: object
+    required: [title]
+    properties:
+      title:   { type: string }
+      content: { type: string, format: markdown, x-body: true }
+      tags:    { type: array, items: { type: string } }
+  list_fields: [title, tags]

package/collection-templates/entity.collection-template.yaml

@@ -0,0 +1,16 @@
+# entity: named things (contacts, suppliers, tools…) — id is the bare name slug,
+# no date prefix (docs-style dated ids read wrong for things that ARE, not happen).
+# storage is left to the template mechanism's standard defaults (data/<name>, md, file).
+name: entity
+template:
+  id:
+    generate: "{{ name | slug }}"
+    pattern: "^[a-z0-9][a-z0-9-]*$"
+  schema:
+    type: object
+    required: [name]
+    properties:
+      name:  { type: string }
+      notes: { type: string, format: markdown, x-body: true }
+      tags:  { type: array, items: { type: string } }
+  list_fields: [name, tags]

package/collections/agents.collection.yaml

@@ -0,0 +1,33 @@
+name: agents
+storage: { path: agents, codec: md, shape: file, suffix: agent }
+id: { generate: "{{ name | slug }}" }
+schema:
+  type: object
+  required: [name, description]
+  properties:
+    name:
+      type: string
+      description: The agent id — must equal the filename, or dispatch misses.
+    description:
+      type: string
+      description: WHEN to dispatch this agent, in one line. The harness matches a request against this, so it is the agent's entire discoverability.
+    tools:
+      type: array
+      items: { type: string }
+      description: The tools this agent may use. Empty means the harness default set.
+    model:
+      type: string
+      description: Which model to run it on. Omit to inherit the session's.
+    skills:
+      type: array
+      items: { type: string, x-reference: skills }
+      description: Skills this agent should load. Reference them rather than restating their steps in the body.
+    instructions:
+      type: string
+      format: markdown
+      x-body: true
+      description: The agent's system prompt — what it is for and how it should work.
+order: 30
+list_fields: [name, last-modified, description]
+icon: smart_toy
+group: system

package/collections/collection-templates.collection.yaml

@@ -0,0 +1,20 @@
+name: collection-templates
+storage: { path: collection-templates, codec: yaml, shape: file, suffix: collection-template }
+id: { generate: "{{ name | slug }}" }
+schema:
+  type: object
+  required: [name, template]
+  properties:
+    name:
+      type: string
+      description: The template id. Scope it to its module (crm-provenance, not provenance) — a template id is an IDENTITY entity, so two modules shipping the same name is a compile-time collision, not a merge.
+    description:
+      type: string
+      description: What field set this template contributes, in one line.
+    template:
+      type: object
+      description: A descriptor stub merged into every collection that names it. Precedence is template < base < overlay, so a descriptor always wins on a key it declares.
+order: 120
+list_fields: [name, last-modified]
+icon: content_copy
+group: system

package/collections/collections.collection.yaml

@@ -0,0 +1,78 @@
+name: collections
+storage: { path: collections, codec: yaml, shape: file, suffix: collection }
+id: { generate: "{{ name | slug }}" }
+schema:
+  type: object
+  required: [name, schema]
+  properties:
+    name:
+      type: string
+      description: The collection id — must equal the filename, and must be unique across every installed module.
+    description:
+      type: string
+      description: What kind of thing this collection holds, in one line.
+    title:
+      type: string
+      description: What to call this collection in the nav and page headers. DERIVED from `name` by title-casing when absent — author it only when that is wrong (`ui-views` → `UI Views`).
+    title_template:
+      type: string
+      description: 'How to label a RECORD of this collection, e.g. `{{ name }}`. DERIVED from the first of title/name/subject the schema declares (else `{{ id }}`). Every reference field pointing at this collection renders its value through this, so it is authored HERE once, not on each referencing field.'
+    extends:
+      type: string
+      description: 'The module collection this one overlays, as `<module>/<collection>`. An overlay adds or narrows fields; it never redefines storage.'
+    storage:
+      type: object
+      description: Where the records live on disk and how they are encoded.
+      properties:
+        path:
+          type: string
+          description: Folder holding the records, workspace-relative. `data/` for content, `state/` for operational records, `system/` for sources.
+        codec:
+          type: string
+          enum: [md, yaml, json]
+          default: md
+          description: File format. Use `md` whenever the record has a body a human will read.
+        shape:
+          type: string
+          enum: [file, folder]
+          default: file
+          description: One file per record, or one folder per record.
+        suffix:
+          type: string
+          description: 'The middle segment of a record filename: `<id>.<suffix>.<ext>`.'
+        entry:
+          type: string
+          description: Folder shapes only — the file inside the folder that IS the record (e.g. SKILL.md).
+        repo:
+          type: string
+          description: DERIVED by compile, never authored — the workspace-relative root of the git repo holding these records ('.' is the workspace). Set from the owning module's `owns-data`.
+    id:
+      type: object
+      description: How a record's id is derived and what shape it is allowed to take.
+      properties:
+        generate:
+          type: string
+          description: 'Template the id is built from, e.g. `{{ created | date }}--{{ name | slug }}`. Derive it from a field the record OWNS, never from write time.'
+        pattern:
+          type: string
+          description: Regex every id must match. `check` enforces it.
+    schema:
+      type: object
+      description: A JSON Schema for the record's fields — validated against the meta-schema, not typed here. A field's own `description:` is what every surface shows as its explanation.
+    order:
+      type: number
+      description: Sort position in the nav. Lower comes first.
+    list_fields:
+      type: array
+      items: { type: string }
+      description: The columns a list view shows by default.
+    icon:
+      type: string
+      description: material-symbols-outlined icon name, drawn in the nav and page header. The VS Code tree maps it to the nearest codicon — an unmapped name falls back to a generic cylinder, so pick one that is already mapped or add the row.
+    group:
+      type: string
+      description: Which nav folder this collection sits in. Ungrouped collections list at the top level; `system` is the plumbing group behind the gear.
+order: 10
+list_fields: [name, last-modified]
+icon: schema
+group: system

package/collections/command-bindings.collection.yaml

@@ -0,0 +1,46 @@
+name: command-bindings
+storage:
+  path: command-bindings
+  codec: yaml
+  shape: file
+  suffix: command-binding
+id:
+  generate: '{{ command | basename }}--{{ collection | basename }}'
+schema:
+  type: object
+  required:
+    - command
+    - collection
+  properties:
+    command:
+      type: string
+      x-reference: commands
+      description: The command this binding applies.
+    collection:
+      type: string
+      x-reference: collections
+      description: The collection the command applies TO — which is what makes `dt commands for <ref>` able to answer "what can I do with this record".
+    target:
+      type: string
+      enum:
+        - record
+        - collection
+      default: record
+      description: Whether the command runs against one record or the whole collection.
+    can-enter:
+      type: object
+      description: The record state that makes this command AVAILABLE — a filter over the record's own fields. This is what turns a collection into a queue without any run records.
+    can-exit:
+      type: object
+      description: The record state that means the command has already been DONE. Together with can-enter, the record's own fields are the progress marker.
+    description:
+      type: string
+      description: What applying this command to this collection does, in one line.
+order: 45
+list_fields:
+  - command
+  - collection
+  - target
+  - last-modified
+icon: bolt
+group: system

package/collections/commands.collection.yaml

@@ -0,0 +1,36 @@
+name: commands
+storage: { path: commands, codec: md, shape: file, suffix: command }
+id: { generate: "{{ name | slug }}" }
+schema:
+  type: object
+  required: [name]
+  properties:
+    name:
+      type: string
+      description: The command id — must equal the filename, and is what the operator types after the slash.
+    description:
+      type: string
+      description: What this command does, in one line. It is the whole entry in the / picker, so write it for someone scanning.
+    # native claude-code slash-command frontmatter — compile copies commands verbatim,
+    # so these flow straight into .claude/commands/<name>.md and the / picker
+    argument-hint:
+      type: string
+      description: What arguments the command takes, shown inline in the / picker.
+    allowed-tools:
+      type: string
+      description: Tools this command may use, when it should be narrower than the session's.
+    model:
+      type: string
+      description: Which model to run it on. Omit to inherit the session's.
+    disable-model-invocation:
+      type: boolean
+      description: Set when only a person may run this — it stops the model invoking it on its own.
+    prompt:
+      type: string
+      format: markdown
+      x-body: true
+      description: The command body. Reference the skill that owns the procedure rather than restating its steps — two copies drift.
+order: 40
+list_fields: [name, last-modified, description]
+icon: terminal
+group: system