| 2026-09-17 |
Document navi-1 (tsukiko) deployment on bugtrail: repo path, service, ports, hive, instance id
...
Deployed navi-1 instance tsukiko on bugtrail (2026-09-17): repo, service, ports, hive announce verified via SSH.
|
Add new LAN VPS bugtrail (192.168.1.177): host doc + hosts inventory item
...
New LAN VPS bugtrail@192.168.1.177 onboarded: read-only SSH recon verified login + sudo (same password), Ubuntu 22.04.5 LTS KVM VM (2 vCPU, 3.8 GiB RAM, 31G LVM), docker+containerd running with no containers, listening ports 22/53/43225, secondary IP 192.168.1.198 on enp1s0 (purpose unknown). Credentials stored in gnexus-creds secret d654f5aa-412b-4fe0-87ad-89cc640375bb. Purpose not yet specified by owner.
|
| 2026-09-16 |
Document navi.service (Navi Proxy, port 8099) on ovpn_reserv
...
Verified via SSH on 2026-09-16: VM ovpn_reserv (192.168.1.226) runs navi.service (systemd, user ubuntu, WorkingDirectory /home/ubuntu/navi-1, ExecStart .venv/bin/navi-server) listening on 0.0.0.0:8099 with /health endpoint. Config at /home/ubuntu/navi-1/.env (OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com). No ollama_backends.json exists. SSH access as user ubuntu (root denied). No secrets stored.
|
Document VM tg_bots (192.168.1.254) navi melody instance and Ollama key rotation
...
New doc 10-systems/servers/tgbots-vm-navi-melody.md: VM tg_bots (192.168.1.254, hostname tgbots) runs mardisbot.service and navi.service (navi instance melody, port 8099, WorkingDirectory /home/ubuntu/navi-1). Ollama API key rotated 2026-09-16 in /home/ubuntu/navi-1/.env; ollama_backends.json not present on this instance; backup .env.bak-ollama-20260916 created; service restarted and verified active with /health HTTP 200.
|
Add 2026-09-16 Ollama key rotation maintenance note to navi-zoe doc
...
Record the 2026-09-16 Ollama API key rotation on the zoe instance and the verified fact that no ollama_backends.json is used.
|
Add service-host (192.168.1.176) doc and inventory: navi zoe instance + GHard panel
...
Rotated Ollama API key on navi zoe instance (192.168.1.176): updated OLLAMA_API_KEY in /home/ubuntu/navi-1/.env, restarted navi.service (active). No ollama_backends.json exists on the host. Documented host and service in gnexus-book (no secret values stored).
|
| 2026-09-12 |
MardisBot: poll schedule moved to Wed+Fri 19:00 Kyiv, PYTHONUNBUFFERED added to unit, backups documented
...
Расписание голосовалок MardisBot изменено 2026-09-12: чт+сб 08:00 → ср+пт 19:00 (days=(3,5), POLL_HOUR=19). Добавлен PYTHONUNBUFFERED=1 в юнит. Бэкапы на VM.
|
| 2026-09-11 |
Мониторинг NFS-шар: 4 шары online, руководство по добавлению
...
Добавлен раздел про мониторинг сетевых шар: текущие 4 шары, пошаговое руководство как добавить новую (mount → compose bind-mount :slave → POST /api/v1/shares → проверка), грабли с docker-compose down/up.
|
| 2026-09-10 |
Document navi zoe deployment on VM service (192.168.1.176)
...
navi zoe deployed on VM service (192.168.1.176) via deploy branch install.sh; joined hive swarm; mcp pinned to 1.27.1; embeddings on local Ollama 192.168.1.168.
|
Fleet hard-monitor: 18/18 серверов online, метод деплоя и грабли
...
Массовый деплой агентов завершён: 18/18 online. Задокументирован fleet-список, неохваченные хосты, метод деплоя и практические грабли (apt 404, py3.6 на gitbucket, диск 100%).
|
Отключён GHARD_ADMIN_TOKEN (UI не работает с токеном), исправлен compose-дефолт, добавлены MCP и заметки
...
UI не показывал сервер из-за GHARD_ADMIN_TOKEN (UI не подписывает запросы токеном) и дефолта change-me в compose. Токен отключён, compose исправлен.
|
Document hard-panel service on 192.168.1.176
...
Deployed GHard Monitor panel (docker) and hard-monitor agent on VM service (192.168.1.176). Secrets in gnexus-creds.
|
Refresh libvirt VM list; document fuckjira at 192.168.1.175
...
fuckjira VM (192.168.1.175) was missing from the VM doc, making .175 appear free. Verified live via virsh + ARP MAC matching on 2026-09-10.
|
Document /backup and ZIP-update in mardisbot remote ops
...
mardisbot.md remote ops section extended: /backup (download code as ZIP) and ZIP-upload update (auto-backup, auto-rollback, .env/venv untouched) now available via MardisOpsBot v2.
|
MardisOpsBot v2 deployed: /backup + ZIP-update, sudoers stop/start, unit ReadWritePaths; tests 18/18
...
v2 deployed to VM tg_bots: /backup + ZIP-update added, sudoers gained stop/start, unit gained ReadWritePaths for MardisBot dir; sandbox tests 18/18 passed. Verified live via SSH.
|
Document NoNewPrivileges fix in mardisops unit
...
mardisopsbot.md: documented removal of NoNewPrivileges=true (it blocked sudo inside the service, broke /status) and the enrolled admin user_id 78389352.
|
Cross-link MardisOpsBot from mardisbot doc
...
Cross-link in mardisbot.md to the new MardisOpsBot remote ops channel (doc 10-systems/bots/mardisopsbot.md).
|
Add MardisOpsBot (mardisops.service) on VM tg_bots
...
Deployed MardisOpsBot on VM tg_bots (192.168.1.254): mardisops.service active (running), enabled; files in /home/ubuntu/bots/MardisOpsBot; sudoers grant /etc/sudoers.d/99-mardisops-sudoers installed and validated. Documented in 10-systems/bots/mardisopsbot.md and services inventory.
|
MardisBot is ACTIVE on VM tg_bots (192.168.1.254); correct host and status
...
Live verification 2026-09-10: MardisBot is running on VM tg_bots (192.168.1.254), not on the tgbots VPS (192.168.1.178). Previous 'missing' status was wrong — the bot was redeployed to the VM after the VPS rebuild.
|
Add 2026-09-10 audit note to tgbots host doc: no Telegram bot currently deployed on the host.
...
2026-09-10 live audit of tgbots found no Telegram bot deployed anywhere on the host; the host doc should record this so future agents do not assume a bot is running.
|
Mark MardisBot as not deployed after 2026-09-10 tgbots audit
...
Exhaustive read-only audit of tgbots (192.168.1.178) on 2026-09-10: no bot processes, no bot systemd units (mardisbot.service absent, no journal history), only marginator docker stack, no cron/tmux/screen, no bot project dirs, zero bot-token matches across /home /opt /srv /etc /usr/local /var, no Telegram API outbound connections, no telegram libraries installed. Host rebuilt ~2026-08-27 and MardisBot was never redeployed.
|
Enrich tgbots host doc: hostname vmk, credentials reference, marginator docker-compose stack details
...
Verified live state via SSH on 2026-06-05: hostname vmk, marginator docker stack running; doc lacked these details.
|
| 2026-09-04 |
Correct gnexus-book deployment facts: VM gnbook 192.168.1.170, repo /home/ubuntu/gnexus-book, endpoints 8000/8001/80, user-level systemd services
...
Live SSH verification on gnbook VM (192.168.1.170): repo path is /home/ubuntu/gnexus-book, not /home/gmikcon/Projects/gnexus-book; endpoints 8000/8001/80 verified; services are user-level systemd units.
|
Document gnexus-auth service; add gnbook VM and gnauth LAN IP to inventory; record shome user on smart-home-server
...
Applied pending changes: 20260904232033-1ff6d9a5 (gnexus-auth service doc), 20260904234541-85929c82 (create gnbook VM item), 20260904234543-e0b90cbe (gnauth LAN IP). VM-to-IP mapping verified via hypervisor ARP + virsh dumpxml MAC correlation on 192.168.1.130. SSH credentials for gnbook/gnauth stored in gnexus-creds (secret gnauth-gnbook-ssh). hosts.yml user:shome addition from earlier verified test session.
|
Add smart-home control playbook: owner rule (no direct device control by default), 4-path hierarchy (CLI action, HTTP API, temp script, restricted device API), safety rules, quick reference.
...
Владелец 2026-09-04 ввёл правило «не управлять устройствами напрямую, дефолт — временные экшины» и попросил описать готовые пути управления. Документ собирает проверенные в этом сеансе факты: 25 живых алиасов, CLI/HTTP пути, паттерн временных скриптов Tier 1, ограниченный device API, правила безопасности.
|
Add exact POST /action wire format for relay devices (live-verified on light_hub_1): mandatory action field, allowed actions set_state/set_channel_state/toggle_channel, 400 without action.
...
Обнаружено при живом включении каналов light_hub_1: три формата тела POST /action без поля "action" отклонены устройством (400 IllegalActionOrParams); рабочий формат найден в исходнике прошивки devices/relay/relay.ino (deviceHandleAction). Фиксирую точный wire-формат, чтобы будущие агенты не тратили попытки на подбор.
|
Tier 1 deployed: GlobalScenesScope with 7 scene actions; live actions 18→25; all-lights-off gap resolved; scope-gate two-pass activation documented; DB counters corrected (45 action / 14 scope rows).
...
Tier 1 scenes deployed and live-verified on shome: GlobalScenesScope with 7 actions (all_lights_off, goodnight, movie_mode, away_toggle, hatch_status, night_mode, guest_mode). Counters re-verified in DB: 45 action rows (42 enabled), 14 scope rows. Coverage gap "no all lights off" resolved.
|
Replace dead alias master_room_lamp_switcher with live master_toggle in bedroom light procedure
...
Live recon 2026-09-04 confirmed master_room_lamp_switcher is a dead alias (not registered by code). The live bedroom action is master_toggle (light_hub_1:1).
|
Fix dead action aliases in API examples; add live-alias warning
...
Live recon 2026-09-04 confirmed the example aliases master_room_lamp_switcher and hallway2_lamp_switcher are dead (not registered by code, return null). Replaced with live aliases master_toggle and hall2_toggle; added a warning pointing to the verified live action list.
|
Add verified modes system, device/channel inventory, device API auth, sensor capabilities, and empty-subsystem facts to smart-home overview
...
Live read-only recon of shome@192.168.1.101 (2026-09-04): modes system and REST API, device/channel inventory, device Bearer auth, sensor firmware capabilities, empty subsystems — none of this was documented.
|