Function normalized_id

atomic-cli/src/commands/intent/bridge.rs:117–127

The normalized intent id used to key BOTH the tracked vault attestation path and the legacy `.atomic` sidecar dir, so the dual-read fallback lines up (critic #4). Resolution mirrors the repository's private `normalize_intent_id` closely enough that `attest 1`, `attest pimo-1`, and `attest PIMO-1` all collapse to the SAME ` ` on both the tracked and the legacy paths: 1. A case-insensitiv

(repo: &Repository, id: &str)

///    manifest stay as the bare number — the same on both paths, so reconciliation
///    still holds).
pub fn normalized_id(repo: &Repository, id: &str) -> CliResult<String> {
    // Resolution lives in exactly one place — the repository resolver — which
    // fills in the current project + author for a bare number, matches full
    // human keys, and resolves ULIDs/prefixes. When nothing resolves (e.g. a
    // reference to an intent with no manifest entry yet), fall back to the
    // uppercased raw arg so `attest` still produces a deterministic sidecar id.
    match repo.resolve_intent_key(id) {
        Ok(key) => Ok(key),
        Err(_) => Ok(id.to_uppercase()),
    }
}

/// The tracked-vault path for an intent's attestation:
/// `attestations/<sanitized-normalized-id>/attested.md`.