feature-manifest 0.7.2

Document, validate, and render Cargo feature metadata.
Documentation
# Cookbook

This page collects short, copy-pasteable workflows for common maintainer tasks.

## Single Crate, First-Time Setup

1. Add or update features in `Cargo.toml`.
2. Scaffold metadata entries:

```text
cargo fm s
```

3. Fill in descriptions and visibility flags.
4. Validate the result:

```text
cargo fm
```

5. Generate Markdown for docs:

```text
cargo fm md -o FEATURES.md
```

## Keep a README Section Up to Date

Add markers to `README.md`:

```markdown
<!-- feature-manifest:start -->
<!-- feature-manifest:end -->
```

Then update that section whenever features change:

```text
cargo fm md -i README.md
```

Use custom markers when your repository already reserves a different region:

```text
cargo fm md -i README.md --start-marker "<!-- features:start -->" --end-marker "<!-- features:end -->"
```

## Fail CI When Metadata Drifts

Use `sync --check` to verify that every feature has metadata and that the
selected layout is already normalized:

```text
cargo fm s --check --style structured
```

Use `check` to enforce quality rules:

```text
cargo fm
```

Use `md --check` to make sure generated docs are committed:

```text
cargo fm md --check -i README.md
```

## Generate Tooling-Friendly Validation Output

For local scripts or editor tooling:

```text
cargo fm c --format json
```

For GitHub Actions annotations:

```text
cargo fm c --format github
```

For code-scanning pipelines:

```text
cargo fm c --format sarif > feature-manifest.sarif
```

## Audit a Workspace

Validate every selected member:

```text
cargo fm -w c -m Cargo.toml
```

Inspect one package in more detail:

```text
cargo fm -p my-crate show serde -m Cargo.toml
```

## Trim Stale Metadata

Remove entries for deleted features and rewrite into a consistent layout:

```text
cargo fm s --remove-stale --style structured
```

Preview whether anything would change without editing the file:

```text
cargo fm s --check --remove-stale --style structured
```

## Soften or Tighten a Lint

Persist the rule in `Cargo.toml`:

```toml
[package.metadata.feature-manifest.lints]
missing-description = "warn"
private-enabled-by-public = "deny"
```

Or override one run from CI:

```text
cargo fm c -l private-enabled-by-public=deny
```

For a broader policy, use a preset:

```toml
[package.metadata.feature-manifest]
preset = "strict"
```