Add camera ingest path details to README and introduce new infrastructure documentation sync skill

pull/1581/head
Carlo Costanzo 1 month ago
parent 2f8f7426e1
commit 91241091ee

@ -37,6 +37,7 @@ Live, personal Home Assistant configuration shared for **browsing and inspiratio
### Platform ### Platform
- Runs on Docker/compose today; this README is a browsing guide, not a how-to-install. Current HA version is tracked in `config/.HA_VERSION` (see the badge above). - Runs on Docker/compose today; this README is a browsing guide, not a how-to-install. Current HA version is tracked in `config/.HA_VERSION` (see the badge above).
- Camera ingest path (current): `wyze-bridge` runs on `docker_10` and Frigate runs on `docker_14`, consuming Wyze RTSP via `192.168.10.10:8554` for stability.
### Featured examples to start with ### Featured examples to start with
- Alarm and perimeter monitoring: [config/packages/alarm.yaml](config/packages/alarm.yaml) - Alarm and perimeter monitoring: [config/packages/alarm.yaml](config/packages/alarm.yaml)

@ -25,6 +25,7 @@ Codex skills stored in-repo so they can be shared with the community. These are
## Skills ## Skills
- `homeassistant-dashboard-designer/`: Constrained, button-card-first Lovelace dashboard design system + YAML lint helper. - `homeassistant-dashboard-designer/`: Constrained, button-card-first Lovelace dashboard design system + YAML lint helper.
- `infrastructure-doc-sync/`: Session closeout workflow to update AGENTS/README/Infra Info snapshot consistently after infra changes.
### Notes ### Notes
- Codex loads skills from your local Codex home. See each skill folder for install steps. - Codex loads skills from your local Codex home. See each skill folder for install steps.

@ -0,0 +1,50 @@
---
name: infrastructure-doc-sync
description: "Use when infra or container placement changes were made in a session and documentation must be synchronized across AGENTS.md, README(s), and Infra Info snapshot (`overview.json`). Covers host maps, role notes, and safe high-level summary updates."
---
# Infrastructure Doc Sync
Keep infrastructure documentation aligned after operational changes.
## When to Use
- Docker service moved between hosts.
- Network mode/port mapping changed.
- Host role changed (core, camera, edge, backup, etc.).
- Any update to an `AGENTS.md` file that affects infra context.
## Required Update Targets
1. `../AGENTS.md` (workspace-level infra truth in `h:\hass\docker_files\AGENTS.md`)
2. Relevant repo README(s), usually:
- `README.md`
- `codex_skills/README.md` (if adding/updating skills)
3. Infra Info snapshot JSON:
- `docker_69:/home/hass/docker_files/infra_info/data/overview.json`
## Workflow
1. Collect current runtime truth from hosts (containers, network mode, ports, and workload role).
2. Update AGENTS host maps and operational notes first.
3. Update README sections impacted by the change (short, factual, no drift).
4. Update `overview.json` to mirror the same outcome at a high level.
5. Validate:
- JSON is valid (`python -m json.tool` equivalent).
- AGENTS and README statements do not conflict with runtime.
## Infra Info Content Rules
- Keep `overview.json` high-level and planning-focused.
- Do not include secrets, tokens, passwords, or internal file paths.
- Avoid step-by-step runbooks.
- Prefer host IDs and roles over low-level implementation detail.
## Output Contract
Always report:
- What changed (files + purpose).
- Final intended topology/placement.
- Any unresolved follow-up items.

@ -0,0 +1,4 @@
interface:
display_name: "Infrastructure Doc Sync"
short_description: "Sync AGENTS/README/overview after infra changes"
default_prompt: "Use $infrastructure-doc-sync to update AGENTS.md, README notes, and infra_info overview.json after Docker/host topology changes."
Loading…
Cancel
Save

Powered by TurnKey Linux.