v0.1.5

Guard local manifests before release

Add a safer project-manifest boundary by treating private .tali manifests as local by default, while preserving explicit shared manifests and adding cached update visibility.

Constraint: Tali must not silently rewrite repository policy or make network checks part of run correctness.

Rejected: Always ignore .tali globally | would remove the shareable project-manifest path.

Rejected: Check for updates on every command without cache | would slow normal CLI usage and create noisy offline failures.

Confidence: high

Scope-risk: moderate

Directive: Keep post-run notices advisory and never let update/gitignore checks change manifest execution status.

Tested: cargo fmt --check; cargo test --locked --all-targets; cargo clippy --locked --all-targets -- -D warnings; cargo check --locked; release metadata, crates version, license, diff checks; manual private/shared manifest and update-check smokes

Not-tested: Full release workflow until tag push