okf-cli 0.1.2__tar.gz → 0.4.1__tar.gz

okf_cli-0.4.1/.github/workflows/test.yml

@@ -0,0 +1,17 @@
+name: Test
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v3
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync
+      - run: uv run pytest -q

okf_cli-0.4.1/.last-update.json

@@ -0,0 +1,5 @@
+{
+  "lastHead": "ddca03b",
+  "lastRun": "2026-07-11",
+  "mode": "update"
+}

okf_cli-0.4.1/AGENTS.md

@@ -0,0 +1,205 @@
+# AGENTS.md — okf-cli contributor context
+
+This file is for AI agents (and humans) picking up work on `okf-cli`.
+
+## OpenWiki (read first)
+
+This repository has docs in `openwiki/`.
+
+Start here:
+
+- [OpenWiki quickstart](openwiki/quickstart.md)
+
+Then follow links to architecture, workflows, domain model, operations, and testing notes relevant to task.
+
+## Project overview
+
+`okf-cli` is a Python CLI that converts plain markdown directories into
+[Open Knowledge Format (OKF)](OKF_SPEC.md) bundles and provides tools to
+inspect/validate them.
+
+- **Input:** plain `.md` files starting with `# Title` and a `>` description block.
+  `bundle` also supports optional `.okfignore` in input root.
+- **Output:** OKF-conformant markdown with YAML frontmatter, per-directory `index.md` files.
+- **Operations:** `bundle`, `list`, `show`, `validate`.
+
+## Tech stack
+
+- Python 3.11+
+- Package/venv manager: **uv**
+- CLI framework: **typer**
+- YAML parsing: **pyyaml**
+- Tests: **pytest**
+- Lint/format: **ruff** (via `uvx ruff check .` / `uvx ruff format .`)
+- Build: hatchling (configured in `pyproject.toml`)
+
+Always use `uv` for dependency sync and running commands:
+
+```bash
+uv sync                  # install/sync deps
+uv run pytest -q           # run tests
+uv run okf --help          # run CLI
+uv run okf bundle example bundled --default-type reference --force
+```
+
+## Project layout
+
+```
+okf-cli
+├── .github/workflows/test.yml # CI (pytest on 3.11)
+├── OKF_SPEC.md              # OKF v0.1 specification
+├── README.md                # user-facing docs
+├── AGENTS.md                # this file
+├── pyproject.toml           # project metadata + deps
+├── uv.lock                  # uv lockfile
+├── src/okf/
+│   ├── cli.py               # Typer entrypoint, registers commands
+│   ├── core.py              # shared parsing/formatting/conformance
+│   └── commands/
+│       ├── bundle.py        # plain markdown → OKF bundle
+│       ├── list.py          # list concept IDs
+│       ├── show.py          # print concept by ID
+│       └── validate.py      # conformance check
+└── tests/test_cli.py        # pytest suite
+```
+
+## Architecture
+
+### `src/okf/cli.py`
+
+- Creates the `typer.Typer` app named `okf`.
+- Registers `bundle`, `list`, `show`, `validate`.
+- No business logic here.
+
+### `src/okf/core.py`
+
+- `RESERVED` — filenames `bundle` skips: `index.md`, `log.md`, `README.md`.
+- `SPEC_RESERVED` — filenames reserved by the OKF spec: `index.md`, `log.md`.
+- `build_frontmatter(...)` — generates YAML frontmatter using JSON-escaped strings.
+- `parse_md(...)` — extracts title/description/body from plain markdown. Tries strict format first (line 1 `# Title`, `>` block); falls back leniently (title from line 0 only, description from first 80 chars of body). Never raises.
+- `parse_frontmatter(...)` — parses YAML frontmatter with `yaml.safe_load`.
+- `check_conformance(...)` — validates a directory against OKF §9, returns `(errors, warnings)`. Now enforces:
+  - §9.1: Non-reserved `.md` must have parseable frontmatter.
+  - §9.2: Frontmatter must have non-empty `type`.
+  - §9.3: `index.md` must not contain frontmatter (§6), except root `index.md` may have only `okf_version` (§11). `log.md` must not contain frontmatter (§7).
+  - Non-UTF-8 files are flagged as errors.
+
+### Commands
+
+| Command    | Input expected                    | Behavior                                                                                                                                                                                                                                                                 |
+| ---------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `bundle`   | non-conformant plain markdown dir | generates OKF bundle; skips `index.md`, `log.md`, `README.md` with warnings; skips `.okfignore`-matched files; checks local `.md` links (warn by default, fail with `--strict-links`); root files need `--default-type`; requires `--force` to overwrite existing output |
+| `list`     | OKF-conformant bundle             | prints concept IDs; exits 1 if dir is not conformant                                                                                                                                                                                                                     |
+| `show`     | OKF-conformant bundle             | prints concept file by ID; exits 1 if dir is not conformant                                                                                                                                                                                                              |
+| `validate` | any directory                     | prints conformance errors and summary per §9                                                                                                                                                                                                                             |
+
+## Key conventions
+
+### Reserved filenames
+
+- `bundle` treats `index.md`, `log.md`, `README.md` as reserved because it
+  often runs against raw repo directories that may contain these files.
+- `list`, `show`, `validate` operate on already-conformant OKF bundles, so
+  they only treat `index.md` and `log.md` as reserved per the spec.
+- `README.md` can be a valid concept in an OKF bundle.
+
+### Link checks in `bundle`
+
+- `bundle` scans markdown body links for local `.md` targets.
+- Supports relative (`./x.md`, `../x.md`) and bundle-root (`/dir/x.md`) links.
+- Ignores external links (scheme URLs like `https:`/`mailto:`), fragment-only links, directory links, and non-`.md` targets.
+- Default behavior: emit warnings for missing local targets or targets outside bundle.
+- `--strict-links`: treat those link issues as fatal and exit non-zero.
+
+### `.okfignore` (bundle only)
+
+- Location: input directory root (`<input-dir>/.okfignore`).
+- Format: one bundle-relative markdown path per line.
+  - Example: `tables/orders.md`, `smoke-ignore.md`
+- Blank lines and lines starting with `#` are ignored.
+- Matching is exact path match only (no glob, no negation).
+- If `.okfignore` is non-UTF-8, `bundle` exits with error.
+
+### OKF conformance (§9)
+
+1. Every non-reserved `.md` must have parseable YAML frontmatter.
+1. Every frontmatter must contain a non-empty `type` string.
+1. Reserved filenames (`index.md`, `log.md`) follow structure per §6/§7 when present.
+   - `index.md` must not contain frontmatter (§6), except root `index.md` may contain only `okf_version` (§11).
+   - `log.md` must not contain frontmatter (§7).
+1. All files must be valid UTF-8.
+
+`check_conformance()` is the source of truth for this logic.
+
+### Frontmatter
+
+`build_frontmatter()` outputs JSON-escaped YAML values, e.g.:
+
+```yaml
+---
+type: "tables"
+title: "Customer Orders"
+---
+```
+
+`parse_frontmatter()` uses `yaml.safe_load()` and returns `None` for missing,
+malformed, or non-dict frontmatter.
+
+## Testing
+
+Run the full suite before finishing:
+
+```bash
+uv run pytest -q
+```
+
+Add tests for new behavior in `tests/test_cli.py`. Existing patterns:
+
+- Unit tests for `core.py` helpers.
+- CLI integration tests using `typer.testing.CliRunner` and `tmp_path`.
+- Conformance tests for `validate`, `list`, `show`.
+
+## Common tasks
+
+### Regenerate the example bundle
+
+```bash
+uv run okf bundle example bundled --default-type reference --force
+uv run okf bundle example bundled --default-type reference --force --strict-links
+uv run okf validate bundled
+uv run okf list bundled
+```
+
+`bundled/` is gitignored; it is only a local artifact. Use `--force` for re-runs.
+If `example/.okfignore` exists, `bundle` will skip matched files.
+
+### Add a new CLI command
+
+1. Create `src/okf/commands/<name>.py` with a function taking `typer` arguments.
+1. Import and register it in `src/okf/cli.py` with `app.command()(fn)` or
+   `app.command("alias")(fn)`.
+1. Add tests in `tests/test_cli.py`.
+
+### Modify conformance behavior
+
+Update `check_conformance()` in `src/okf/core.py`, then ensure
+`validate`, `list`, and `show` all behave consistently.
+
+## Style guidelines
+
+- Keep changes minimal. Prefer stdlib/installed dependencies over new ones.
+- Do not add abstractions "for later".
+- Use `Path` from `pathlib`, not string path manipulation.
+- Use `uv` for all package/runtime commands.
+
+## OpenWiki
+
+This repository has documentation located in the /openwiki directory.
+
+Start here:
+
+- [OpenWiki quickstart](openwiki/quickstart.md)
+
+OpenWiki includes repository overview, architecture notes, workflows, domain concepts, operations, integrations, testing guidance, and source maps.
+
+When working in this repository, read the OpenWiki quickstart first, then follow its links to the relevant architecture, workflow, domain, operation, and testing notes.

{okf_cli-0.1.2 → okf_cli-0.4.1}/OKF_SPEC.md

@@ -12,7 +12,7 @@ YAML frontmatter. There is no schema registry, no central authority, and
 no required tooling. If you can `cat` a file, you can read OKF; if you
 can `git clone` a repo, you can ship it.
 
----
+______________________________________________________________________
 
 ## 1. Motivation
 
@@ -33,9 +33,9 @@ of structural conventions needed to make a knowledge corpus
 ### Goals
 
 1. Define a universal format that **enrichment agents** can write into.
-2. Inform how **consumption agents** should read and traverse it.
-3. Facilitate **exchange** of knowledge across systems and organizations.
-4. Standardize the small number of **required** fields that must be
+1. Inform how **consumption agents** should read and traverse it.
+1. Facilitate **exchange** of knowledge across systems and organizations.
+1. Standardize the small number of **required** fields that must be
    present for content to be meaningfully consumed.
 
 ### Non-goals
@@ -45,7 +45,7 @@ of structural conventions needed to make a knowledge corpus
 - Replacing domain-specific schemas (Avro, Protobuf, OpenAPI, etc.) —
   OKF *references* them; it does not subsume them.
 
----
+______________________________________________________________________
 
 ## 2. Terminology
 
@@ -66,7 +66,7 @@ of structural conventions needed to make a knowledge corpus
 - **Citation** — A link from a concept to an external source that
   supports a claim in the body.
 
----
+______________________________________________________________________
 
 ## 3. Bundle Structure
 
@@ -97,10 +97,10 @@ A bundle MAY be distributed as:
 The following filenames have defined meaning at any level of the
 hierarchy and MUST NOT be used for concept documents:
 
-| Filename     | Purpose                                                |
-|--------------|--------------------------------------------------------|
-| `index.md`   | Directory listing. See §6.                             |
-| `log.md`     | Update history. See §7.                                |
+| Filename   | Purpose                    |
+| ---------- | -------------------------- |
+| `index.md` | Directory listing. See §6. |
+| `log.md`   | Update history. See §7.    |
 
 All other `.md` files are concept documents.
 
@@ -109,7 +109,7 @@ frontmatter field in §4.1. OKF does not specify a separate file format
 for aggregating documents by tag; producers that want a tag-browsing
 view can synthesize one at consumption time by scanning frontmatter.
 
----
+______________________________________________________________________
 
 ## 4. Concept Documents
 
@@ -117,7 +117,7 @@ Every concept is a UTF-8 markdown file. It has two parts:
 
 1. A **YAML frontmatter block**, delimited by `---` on its own line at
    the start of the file and a closing `---` on its own line.
-2. A **markdown body**, containing free-form content.
+1. A **markdown body**, containing free-form content.
 
 ### 4.1 Frontmatter
 
@@ -170,11 +170,11 @@ prose, since structure aids both human reading and agent retrieval.
 There are no required body sections. The following section headings have
 **conventional** meaning and SHOULD be used when applicable:
 
-| Heading        | Purpose                                                |
-|----------------|--------------------------------------------------------|
-| `# Schema`     | Structured description of an asset's columns/fields.   |
-| `# Examples`   | Concrete usage examples, often as fenced code blocks.  |
-| `# Citations`  | External sources backing claims in the body. See §8.   |
+| Heading       | Purpose                                               |
+| ------------- | ----------------------------------------------------- |
+| `# Schema`    | Structured description of an asset's columns/fields.  |
+| `# Examples`  | Concrete usage examples, often as fenced code blocks. |
+| `# Citations` | External sources backing claims in the body. See §8.  |
 
 ### 4.3 Example: a concept bound to a resource
 
@@ -228,7 +228,7 @@ its expected SLA. See the [orders table](/tables/orders.md).
 2. …
 ```
 
----
+______________________________________________________________________
 
 ## 5. Cross-linking
 
@@ -266,7 +266,7 @@ Consumers MUST tolerate broken links — a link whose target does not
 exist in the bundle is not malformed; it may simply represent
 not-yet-written knowledge.
 
----
+______________________________________________________________________
 
 ## 6. Index Files
 
@@ -293,7 +293,7 @@ Entries SHOULD include the description from the linked concept's
 frontmatter. Producers MAY generate `index.md` automatically; consumers
 MAY synthesize one on the fly when none is present.
 
----
+______________________________________________________________________
 
 ## 7. Log Files (optional)
 
@@ -317,7 +317,7 @@ Date headings MUST use ISO 8601 `YYYY-MM-DD` form. Log entries are
 prose; the leading bold word (`**Update**`, `**Creation**`,
 `**Deprecation**`, etc.) is a convention, not a requirement.
 
----
+______________________________________________________________________
 
 ## 8. Citations
 
@@ -336,7 +336,7 @@ Citation links MAY be absolute URLs, bundle-relative paths, or paths
 into a `references/` subdirectory that mirrors external material as
 first-class OKF concepts.
 
----
+______________________________________________________________________
 
 ## 9. Conformance
 
@@ -344,8 +344,8 @@ A bundle is **conformant** with OKF v0.1 if:
 
 1. Every non-reserved `.md` file in the tree contains a parseable YAML
    frontmatter block.
-2. Every frontmatter block contains a non-empty `type` field.
-3. Every reserved filename (`index.md`, `log.md`) follows the structure
+1. Every frontmatter block contains a non-empty `type` field.
+1. Every reserved filename (`index.md`, `log.md`) follows the structure
    described in §6 and §7 respectively when present.
 
 Consumers SHOULD treat all other constraints as soft guidance. In
@@ -361,7 +361,7 @@ This permissive consumption model is intentional: OKF is meant to
 remain useful as bundles grow, get refactored, and are partially
 generated by agents.
 
----
+______________________________________________________________________
 
 ## 10. Relationship to other formats
 
@@ -377,7 +377,7 @@ OKF is intentionally close to several established patterns:
 OKF differs primarily in being **specified** — pinning down the small
 set of rules needed for interoperability without dictating tooling.
 
----
+______________________________________________________________________
 
 ## 11. Versioning
 
@@ -395,7 +395,7 @@ only place frontmatter is permitted in an `index.md`). Consumers that
 do not understand the declared version SHOULD attempt best-effort
 consumption rather than refusing the bundle.
 
----
+______________________________________________________________________
 
 ## Appendix A — Minimal example bundle
 

okf_cli-0.4.1/PKG-INFO

@@ -0,0 +1,257 @@
+Metadata-Version: 2.4
+Name: okf-cli
+Version: 0.4.1
+Summary: Open Knowledge Format tooling
+License: MIT License
+        
+        Copyright (c) 2026 Dheerapat Tookkane
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: pyyaml>=6
+Requires-Dist: typer>=0.15
+Description-Content-Type: text/markdown
+
+# okf-cli — Open Knowledge Format tooling
+
+Converts plain markdown into [OKF](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md)-conformant knowledge bundles. Domain experts write `# Title` then `> description` — `okf bundle` generates frontmatter, type, timestamps, and index files. Files without strict formatting are parsed leniently: title from line 0 if present, description from body text.
+
+Also validates bundles and lists concept IDs for consumption by other tools.
+
+## Install
+
+```bash
+uv tool install okf-cli
+```
+
+### Dev quickstart
+
+```bash
+uv sync
+uv run okf --help
+```
+
+## Commands
+
+### `okf bundle` — convert plain markdown to OKF bundle
+
+```
+okf bundle <input-dir> [output-dir] [--default-type <name>] [--force] [--strict-links]
+```
+
+| Argument         | Description                                                                  |
+| ---------------- | ---------------------------------------------------------------------------- |
+| `input-dir`      | Directory of plain `.md` files                                               |
+| `output-dir`     | Target directory (default: `bundled`)                                        |
+| `--default-type` | Type for root-level files (skip root files if omitted)                       |
+| `--force`, `-f`  | Overwrite output directory if it exists                                      |
+| `--strict-links` | Fail if local markdown links point outside bundle or to missing `.md` target |
+
+```bash
+okf bundle example --default-type reference  # first run → bundled/
+okf bundle example --default-type reference --force  # re-run
+okf bundle example --default-type reference --force --strict-links  # fail on broken local .md links
+cat bundled/tables/orders.md
+```
+
+`.okfignore` (bundle only):
+
+- Put `.okfignore` in `input-dir`.
+- Add bundle-relative markdown paths to skip, one per line.
+- Blank lines and `#` comments ignored.
+- Matching is exact path match (no glob, no negation).
+
+```text
+# example/.okfignore
+smoke-ignore.md
+tables/orders.md
+```
+
+Local link checks during `bundle`:
+
+- Scans markdown body links to local `.md` targets.
+- Supports relative links (`./x.md`, `../x.md`) and bundle-root links (`/tables/x.md`).
+- Ignores external links (`https:`, `mailto:`), fragment-only links (`#section`), directory links, and non-`.md` targets.
+- Default mode prints warnings for missing targets or links resolving outside bundle.
+- `--strict-links` turns those warnings into a non-zero exit (`Error: strict link check failed`).
+
+### `okf list` — list concept IDs in a bundle
+
+```
+okf list <directory>
+```
+
+Prints concept IDs (bundle-relative path with `.md` stripped) for every
+concept file in the bundle. Reserved filenames (`index.md`, `log.md`)
+are excluded. `README.md` is not reserved by the OKF spec and is listed
+as a concept if present.
+
+Requires the directory to be a valid OKF bundle; fails if any
+non-reserved `.md` is missing frontmatter or a non-empty `type`.
+
+```bash
+okf list bundled/
+# datasets/sales
+# playbooks/incident-response
+# tables/orders
+# …
+```
+
+Useful for piping OKF bundles into other tooling:
+
+```bash
+okf list bundled/ | xargs -I{} okf show bundled/ {}
+```
+
+### `okf show` — read a concept by ID
+
+```
+okf show <directory> <concept-id>
+```
+
+Prints the full contents (frontmatter + body) of a concept file.
+Concept IDs are the bundle-relative path with `.md` stripped — exactly
+as printed by `okf list`.
+
+Requires the directory to be a valid OKF bundle.
+
+```bash
+okf show bundled/ tables/orders
+# ---
+# type: "tables"
+# title: "Customer Orders"
+# ...
+```
+
+Guards against path traversal and rejects reserved filenames.
+
+### `okf validate` — check OKF conformance
+
+```
+okf validate <directory>
+```
+
+Checks OKF v0.1 §9 conformance:
+
+- Every non-reserved `.md` has parseable YAML frontmatter with non-empty `type`.
+- Reserved filenames (`index.md`, `log.md`) follow spec structure (§6/§7).
+- Non-UTF-8 files are flagged.
+
+```bash
+okf validate bundled/
+# 16 files: 16 ok
+```
+
+## Writing input files (for `bundle`)
+
+### Strict format (recommended)
+
+Every `.md` file starts with:
+
+```markdown
+# Title
+
+> Description
+> Second optional description line.
+```
+
+Everything after the description block is preserved unchanged.
+
+### Lenient fallback
+
+Files that don't follow the strict format are still bundled best-effort:
+
+| Condition                                | Behavior                                                           |
+| ---------------------------------------- | ------------------------------------------------------------------ |
+| No `# Title` on line 1                   | Title omitted from frontmatter                                     |
+| No `>` description block                 | Description derived from first 80 chars of body ("…" if truncated) |
+| Root-level file without `--default-type` | Skip file, warn, continue                                          |
+
+**Rules:**
+
+| Rule                                                  | Why                                                                                                                                                                                                                         |
+| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Folder name = concept type                            | `tables/orders.md` → `type: "tables"`                                                                                                                                                                                       |
+| Only `.md` files processed                            | Non-`.md` files ignored                                                                                                                                                                                                     |
+| `index.md`, `log.md`, `README.md` skipped in `bundle` | Input may contain repo artifacts; these are not concepts. `bundle` warns when it skips them. Other commands (`list`, `show`, `validate`) operate on conformant OKF bundles where only `index.md` and `log.md` are reserved. |
+| `.okfignore` entries skipped in `bundle`              | Add bundle-relative markdown paths (e.g. `tables/orders.md`) to skip conversion for selected files. Blank lines and `#` comments are ignored.                                                                               |
+
+Root files need `--default-type`. Otherwise put files in named folders.
+
+See the [`example/`](example/) directory for a sample of how to structure files.
+
+## How `bundle` works
+
+1. Walk `input-dir` for `.md` files (skip `.okfignore` matches and reserved names)
+1. Extract `title` from `#` on line 1, `description` from `>` block. If strict format not met, falls back: title omitted if absent, description from first 80 chars of body
+1. Check local markdown links against planned bundle targets (warn by default, or fail with `--strict-links`)
+1. Set `type` from parent dir name, `timestamp` from file mtime
+1. Write concept files with YAML frontmatter (title field omitted if empty)
+1. Generate `index.md` per directory — `# Contents` for files, `# Directories` for subdirs (recursive)
+
+## Output
+
+Each concept becomes a markdown file with YAML frontmatter:
+
+```yaml
+---
+type: "tables"
+title: "Customer Orders"
+description: "One row per completed customer order across all channels."
+timestamp: "2026-07-04T15:06:51+00:00"
+---
+
+Original body preserved as-is.
+```
+
+Every directory gets its own `index.md`:
+
+```markdown
+# Contents
+
+* [Customer Orders](orders.md) - One row per completed customer order across all channels.
+
+# Directories
+
+* [partitions](partitions/)
+```
+
+## OKF Conformance
+
+Generated bundles conform to [OKF v0.1](OKF_SPEC.md) (§9):
+
+- Every non-reserved `.md` has parseable YAML frontmatter with non-empty `type` ✓
+- Reserved filenames follow spec structure ✓
+- Consumers MUST tolerate missing optional fields, unknown types, broken links ✓
+
+## Project layout
+
+```
+okf-cli
+├── .github/workflows/test.yml  # CI
+├── OKF_SPEC.md                 # OKF specification
+├── pyproject.toml              # uv-managed Python project
+├── src/okf/
+│   ├── cli.py            # Typer entrypoint
+│   ├── core.py           # Shared parsing/formatting
+│   └── commands/         # bundle, list, show, validate
+├── tests/test_cli.py     # Tests
+└── example/              # Sample input markdown
+```