FlowMark-core

Core CLI for FlowMark v0.1.6.

Install (npm)

npm install @flowmark/core-cli

Usage

flowmark validate path/to/file.md
cat path/to/file.md | flowmark validate
flowmark parse path/to/file.md
flowmark lint path/to/file.md
flowmark describe ai
flowmark describe ai-source
flowmark describe ai --lang en --format md
flowmark params normalize --lang en --format md

Options

• --strict : strict mode
• --lenient : lenient mode (default)
• --stdin : read from STDIN even if file is provided
• --version
• --help

Docker

Image: ghcr.io/centimanidevteam/flowmark-core-cli

docker run --rm -v "$(pwd)":/work -w /work ghcr.io/centimanidevteam/flowmark-core-cli validate path/to/file.md
cat path/to/file.md | docker run --rm -i -v "$(pwd)":/work -w /work ghcr.io/centimanidevteam/flowmark-core-cli validate --stdin

Test Samples (MVP)

node bin/flowmark.js validate docs/dev/v0.1.4/samples/minimal.md
node bin/flowmark.js validate docs/dev/v0.1.4/samples/spec-conformant.md
node bin/flowmark.js validate docs/dev/v0.1.4/samples/ai-template.md

Note: If E_YAML_PARSE occurs, derived errors/warnings (e.g. E_ITEM_NONE, W_REGISTRY_MISSING) are suppressed.

Strict vs Lenient (Example)

node bin/flowmark.js validate docs/dev/v0.1/samples/lenient-unexpected.md
node bin/flowmark.js validate --strict docs/dev/v0.1/samples/lenient-unexpected.md

In lenient, unexpected items are warnings (W_UNEXPECTED_ITEM).
In strict, they become errors (E_UNEXPECTED_ITEM).

Unknown Keys Warning

Unknown keys are allowed but produce W_UNKNOWN_KEYS warnings. Extension keys (x_*, x-...) are exempt.

npm pack (Publish Check)

npm pack
tar -tf flowmark-core-cli-0.1.6.tgz

Check that bin/, src/, README.md, and LICENSE are included.