# 2026-04-17

- Recovered access to `ruvpn` (host `ru-vmpico` / `185.130.212.192`) after UFW had blocked SSH.
- On console, enabled UFW ports `22/tcp`, `3322/tcp`, and `13981/tcp`; SSH service is active.
- SSH access initially worked only on port 22; then `sshd_config` was updated to listen on both `22` and `3322` after making a backup.
- `x-ui.service` and `xray.service` are active on `ruvpn`.
- Confirmed 3x-ui is reachable via `https://185.130.212.192:37615/Tlvziqv5coI64Ymq5U/`.
- Shared a working Happ/VLESS Reality config for the current inbound on `185.130.212.192:13981`.
- Learned that 3x-ui webUI can manage inbounds, but cannot fix host-level UFW/SSH issues; console access was required.
- QMD embed process was identified as a heavy background CPU/RAM consumer on the `legal` agent, but waiting was chosen instead of interrupting it.
- New project established: VPN chain `Android (v2raytun) -> ruvpn -> 43.245.226.231 (VLESS Reality) -> internet`.
- Project file created: `tasks/vpn-chain/PROJECT.md`.
- On `ruvpn`, created outbound to `43.245.226.231:53903` and routing rule from `inbound-41539` to that outbound, then verified the chain worked.

- Ontology status check: `memory/ontology/graph.jsonl` exists, `memory/ontology/schema.yaml` exists, but ontology queries are currently broken by malformed JSONL.
- Specific failure observed: `python3 skills/ontology/scripts/ontology.py query ...` throws `JSONDecodeError: Expecting ',' delimiter` while reading `graph.jsonl`.
- Conclusion: ontology data is present but one JSONL record near the end is malformed; it needs repair rather than full rebuild.
