Infrawise v1.0.0

Infrawise 1.0 brings infrastructure context and pre-deployment checks together with clearer evidence, privacy boundaries, and freshness controls.

Behavior changes

• infrawise check exits with code 2 when extraction or analyzers are incomplete. Use --allow-incomplete only when intentionally accepting missing coverage; blocking findings still fail.
• get_log_errors now returns log group retention metadata only. Error counts are null, patterns are empty, and log message bodies are never requested.
• Existing analysis caches are invalidated so older sampled log patterns are discarded.

Improvements

• PostgreSQL and MySQL index analysis considers ordered composite indexes and supported predicates, with conservative warnings where metadata is uncertain.
• Every MCP response reports recognized code coverage and refresh failures, avoiding unsupported claims about missing resources or access.
• Optional freshness.refreshIntervalMinutes performs serialized full background analysis after snapshot loading. It is disabled by default.
• Added assistant workflow guidance, an evaluation harness, reproducible performance benchmarks, and database demo smoke tests.
• Updated documentation and demo coverage across the CLI and 22 MCP tools.

Validation

522 tests passed, alongside build, coverage, documentation and website checks. PostgreSQL, MySQL, MongoDB, LocalStack and Floci demos were exercised. Floci matched 56 findings, 47 nodes and 15 edges with all enabled sources healthy.

Static scanning covers recognized patterns and does not prove complete runtime access. Index warnings are not observed query plans. Background refresh bounds snapshot age and does not detect deployment events instantly.