# Changelog

## Score

- CAI 58 → 58 (-0.2)

## Lenses

- Code Health 96 → 96 (+0.0)
- Architecture 93 → 93 (+0.0)
- Maturity 56 → 55 (-0.7)
- Readiness 58 → 58 (+0.0)
- Security 49 → 49 (-0.1)
- Performance 100 → 100 (+0.0)

## Resolved (6)

- Ambiguous operation naming. `open` and `open_or_create` are semantically distinct (one likely fails if missing, the other creates), but the naming convention is inconsistent with common Rust patterns where `open` often implies creation if missing (like `File::open` on some systems) or requires a separate `create` method. More critically, having both `open` and `open_or_create` suggests `open` might be a legacy or restricted version, which is confusing for API users.
- Duplicate/Shadowed function names. `innernet_shared::get_local_addrs` exists alongside `innernet_shared::_get_local_addrs`. The underscore prefix typically indicates a private or deprecated alias, but both are exposed in the public module surface. This creates confusion about which function to use.
- Inconsistent naming for path resolution methods. `database_path` and `config_path` are clear, but `DataStore.get_path` (in a different module) also resolves paths. While domains differ, the verb 'get_path' is generic compared to the specific 'config_path'/'database_path'. More importantly, `InterfaceConfig.get_path` exists alongside `InterfaceConfig.build_config_file_path`. `get_path` is generic, `build_config_file_path` is specific. This inconsistency in verb choice (`get` vs `build`) for similar path-resolution intents is confusing.
- Off-boarding risk: anonymized user #1
- Redundant save operations with different signatures. `save_new` takes a raw path and mode, while `save` takes a config dir and interface name to derive the path. This duplicates the intent of persisting configuration but forces the caller to choose between low-level path control and high-level interface-based resolution without a clear hierarchy.
- Workflow token permissions not restricted

## New (18)

- Medium advisory (unsound): RUSTSEC-2026-0386 (Cargo.lock)
- Off-boarding risk: anonymized user #1
- Orphaned file (publicip/src/lib.rs)
- Orphaned file (server/src/api/admin/cidr.rs)
- Orphaned file (server/src/api/mod.rs)
- Orphaned file (server/src/db/association.rs)
- Orphaned file (server/src/db/cidr.rs)
- Orphaned file (server/src/db/peer.rs)
- Orphaned file (server/src/main.rs)
- Orphaned file (server/src/test.rs)
- Orphaned file (shared/src/netlink.rs)
- Orphaned file (shared/src/wg.rs)
- Orphaned file (wireguard-control/src/backends/openbsd.rs)
- Orphaned file (wireguard-control/src/backends/userspace.rs)
- Orphaned file (wireguard-control/src/config.rs)
- Orphaned file (wireguard-control/src/key.rs)
- Workflow token permissions not restricted (.github/workflows/docker-tests.yml)
- Workflow token permissions not restricted (.github/workflows/rust.yml)
