# Verification record — `tsidentity-import-spike`

## Result

PASS. The sample TeamSpeak identity file imported successfully, exported back to
the exact same identity string, and was usable for a live connection to
`kr.teamspeak.app`.

## Environment

| Field | Value |
|---|---|
| Date | 2026-05-25 |
| Host OS | Linux (x86_64) |
| Build profile | test + dev |
| Target server | `kr.teamspeak.app` |

## Commands

```bash
cargo test --offline

cargo run --offline -- \
  --identity-file /path/to/exported_identity.ini \
  --address kr.teamspeak.app
```

## What was observed

- Unit test passed:
  - exported identity INI parsed successfully
  - exported identity string matched the original exactly
- Imported sample identity properties:
  - nickname: `Edison.Jwa`
  - UID: `eaRkG62hRaLs+R9sOuOWK7xbnUY=`
  - security level: `8`
  - counter: `40`
- Live connect using the imported identity succeeded:
  - connected nickname: `Edison.Jwa`
  - connected UID: `eaRkG62hRaLs+R9sOuOWK7xbnUY=`
  - connected DBID: `17225`
  - connected CLID: `18506`
  - connected CID: `1`
  - country: `KR`
  - server groups: `{ServerGroupId(8)}`

## Important finding

The provided sample identity is **not** the live `EdisonJwa` identity currently
online on `kr.teamspeak.app`.

- Sample imported identity UID: `eaRkG62hRaLs+R9sOuOWK7xbnUY=`
- Live `EdisonJwa` UID from the query spike: `QcnldW6Qnw/4im/t94j/FYIcVMU=`

That means:

- the import/export implementation is working, and
- the sample INI belongs to a different TeamSpeak identity than the live
  `EdisonJwa` account used in the example profile.