docs: finish questions consolidation — drop merged files [#344]

Leftover unstaged state from the parallel 09-02 sessions: delete questions-v1/v2, HomeAssistant/needfromcharles.md, night-grind-plan.md (content lives in questions-09022206.md / questions-v3.md / git history); drop superseded UniFi API-key ask (#619 multicast fix made it moot). Details: https://projects.knownelement.com/issues/344#note-3911
2026-09-02 18:26:14 -05:00
parent 0c6aabbb4d
commit 77811927e3
5 changed files with 2 additions and 163 deletions
@@ -1,4 +0,0 @@
 # needfromcharles.md — SUPERSEDED 2026-09-02
 Consolidated into `questions-09022206.md` (repo root). Do not add asks here.
 Knowledge docs: https://community.turnsys.com/c/vp-techops
@@ -1,33 +0,0 @@
 # night-grind-plan.md — unattended session plan (2026-09-01 → 09-02)
 > Approved-scope working file; knowledge docs on Discourse: https://community.turnsys.com/c/vp-techops
 > Founder answers to blocking questions land in HomeAssistant/needfromcharles.md — check it at each phase.
 ## Phase order (each ends verified + documented; tickets/audit updated per item)
 1. **Verify Server-Room dashboard rendered** (commit 88f2a53; auto-restart fired).
   `lovelace` dashboards list via websocket; confirm pfv-server-room present.
 2. **SNMP temp migration** [#618] — temps live end-to-end:
   a. TDD: `-n` numeric mode (plain °C float) in dcinfra/sensors/temper/lmsensors-extend.sh
   b. Deploy `lmsensors_n` extend to the 6 hosts (#458 pattern, serial)
   c. 16 SNMP config entries via REST flow (host+community+manual OID, device_class temperature)
   d. Remove dead packages/plant-snmp.yaml from KNEL/pfv-bms; verify sensors in areas + dashboard
 3. **Cloudron global HA** [#626]: version check (needs ≥2025.7) → mint pfv-bms long-lived
   token (websocket `auth/long_lived_token`) → configure remote pairing on
   building-management.knownelement.com → verify pfv-bms entities visible there.
 4. **Privacy scoping** [#627]: per-user dashboards; health/location entities hidden from
   non-founder users; document residual ACL limits.
 5. **iDRAC probes** [#625]: DNS/port probe pfv-tsys6-oob + pfv-tsys7-oob; Redfish walk if
   live; wire into LibreNMS or HA where trivial; report otherwise.
 6. **Backup + hygiene**: `ha backups new` (verify), docker image prune (~6GB), Grafana
   datasource check + starter Server-Room dashboard (grafana env at ~/.creds/grafana.env).
 7. **Docs**: Discourse topic for HomeAssistant ops (point HomeAssistant/README.md at it),
   audit-log entry, WORKING.md, ticket notes.
 ## Explicitly NOT tonight (needs founder or hardware)
 - UniFi AP mDNS/multicast toggle (#619) — READ-ONLY inspection at most; change needs approval
 - Midea token / HomeKit pairing / Govee devices / Emporia / Tripp Lite — see
  HomeAssistant/needfromcharles.md + Friday #629
 - k8s rebuild (#367/#368) — timing decision pending
 - HA high availability (#628) — founder-excluded
 - Any restart of BOTH members of a redundant pair (hard rule)
@@ -2,8 +2,8 @@
 # questions-09022206.md — consolidated open asks (2026-09-02)
 > Merged from `questions-v2.md` (repo root) + `HomeAssistant/needfromcharles.md`
-> per founder request. That file is now a pointer; questions-v2.md stays as
+> per founder request; both source files since removed (history in git).
-> history. Answer inline; agent checks before asking again.
+> Answer inline; agent checks before asking again.
 ## HA / monitoring (was needfromcharles)
@@ -25,9 +25,6 @@ Integration live (key+account+MQTT); account has ZERO cloud devices = BLE-only.
 ### 4. Emporia Vue 3 — blocks #623 (BTU loop)
 - [ ] Ordered? ETA:
 ### 8. UniFi Integration API key — LOW priority now (multicast fix works)
 - [ ] (optional) Settings → System → Advanced → Integrations → API Keys
 ### 9. iDRAC — RESOLVED 2026-09-02
 [x] Creds worked; both SNMP agents live; tsys6 `public` accepted by founder.
@@ -1,61 +0,0 @@
 # questions-v1.md
 > Git-tracked question log. The agent writes; the human reviews/edits inline.
 > Version up when a round of answers lands. Synthesize resolved Q&A to Discourse/Redmine.
 > See BASELINE-PROMPT.md §9.
 ## Open questions
 ### Q1. Git remote for meta?
 - **Context:** meta is now a git repo (locally) but has no remote configured. The auto-commit+push policy (baseline §4) can't complete without one.
 - **Options:** (a) new Gitea repo under reachableceo; (b) nest under an existing repo; (c) keep local-only for now.
 - **Question:** Where should meta push?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 Go with option a. The tea command is setup on this workstation (and on ultix-offstage). I guess, also capture that the tea command (and docker login) are setup on my workstations, so that in the future, projects know they can use tea to setup a repo. Also, i want this to be TSYS wide, so it should go under the TSYSGroupCorporate organization. Call the repo: TSYSGroupAIOS . Make it a template repository.
 ### Q2. The bin/ wrapper gap (redmine-cli / discourse-cli) — RESOLVED (discourse)
 - **Context:** PFVCluster's operational.md and AGENTS.md referenced `~/daytoday/redmine/bin/redmine` and `~/daytoday/discourse/bin/discourse` as the entrypoints — thin shortcut wrappers around the real CLI containers. The actual CLI source lived in `~/projects/KNEL-AIMiddleware/{redmine,discourse}-cli/`.
 - **Question:** Are the `bin/` wrappers something that should exist, or is the documentation aspirational? Should the template reference these CLIs at all, or stay tool-agnostic?
 - **Answer:** Reference the real container invocation (full path/container name/invoke notes); no duplicate code via shortcut wrappers.
 - **Decision:** No `bin/` wrappers. Invoke the real container with `docker run`. Both CLI sources have been merged into `~/projects/KNEL-AIMiddleware/tooling-cli/{discourse,redmine}/` and PFVCluster's AGENTS.md now invokes them via `docker run --env-file ~/.creds/{discourse,redmine}.env`. The old `~/daytoday/{discourse,redmine}` workspaces and the `{discourse,redmine}-cli/` subdirs were removed.
 - **Synthesized to:** PFVCluster `AGENTS.md` §CLI access; `tooling-cli/{discourse,redmine}/`
 ### Q3. Should the template ship the Discourse pointer-header pattern?
 - **Context:** PFVCluster migrated 36 in-repo `.md` files to 10-line pointer stubs citing `https://community.turnsys.com/t/<N>`. The template currently has `scripts/garden.sh` that *warns* about oversized non-Discourse `.md`, but doesn't enforce the pointer-header format.
 - **Options:** (a) keep it advisory (garden.sh warn only); (b) add an opt-in check-rule that fails if a tracked `.md` lacks a Discourse URL (excluding AGENTS.md/STATUS.md/etc.); (c) leave it project-local — infra projects want it, personal/business projects don't.
 - **Question:** Which option, and is the assumption in (c) right?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 All projects need it. Discourse/redmine is MANDATORY. No exceptions. What is project specific is which categories to use, and maybe some tagging/topic guidelines etc.
 ### Q4. Sub-agent nudge hook — wanted?
 - **Context:** A sub-agent proposed a non-blocking Crush hook (`hooks/nudge-subagent.sh`) that emits a stderr reminder after the Nth sequential file read, nudging toward dispatching a sub-agent. Mirrors football's "never read 10+ files sequentially" rule.
 - **Options:** (a) add it (non-blocking, advisory); (b) leave sub-agent use as prose policy only.
 - **Question:** Worth adding, or too noisy?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 Preseving tokens/quota burn is a HUGE priority. It lets me and you do far more work for much longer. Also, I want to move away from harness specific hooks. Git hooks/strong AGENTS.md protocols are strongly preferred. Ill be shifting away from crush over next few weeks to using OpenWebUi/Hermes and a whole swarm of agents with reporting/working relationships etc etc. So anything that is harness specific, get rid of it and make it portable.
 ### Q5. JOURNAL.md vs Discourse audit-log for infra projects
 - **Context:** The template ships `docs/JOURNAL.md` as the append-only decision log. But PFVCluster (the most mature infra project) has NO JOURNAL.md — it uses Discourse topic #298 as the audit log and Redmine for work tracking. PATTERNS.md §5 noted this divergence.
 - **Question:** Should the template keep JOURNAL.md as the default, with infra projects swapping it for the Discourse-audit-log pattern? Or drop JOURNAL.md entirely in favor of "Discourse is the SoR"?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 No more JOURNAL.md . Redmine is the system of record. JOURNAL.md was a hack I was using until redmine integration was in place. And, yes, discourse can also be used as well. Its a bit of a tricky decision, what should go to redmine vs discourse. I usually keep working notes/evolving status etc in Redmine and then synthesize to Discourse. But thats me as a lowly human :) You figure it out as you go and per project.
 ### Q6. RackRental split-network design on pfv-tsys6/7 [#433]
 - **Context:** TSYS6 and TSYS7 need trunk ports for RackRental. Servers will run a "split network configuration — half on the non-RackRental switch/router side, half on the RackRental switch/router side." RackRental router prevents network loops.
 - **Question:** Is the split per-NIC (one physical NIC to normal network, one to RackRental) or per-VM (some VMs bridge to RackRental, some to normal)? Both TSYS6/7 currently have bond0 with 2 slaves for storage network. How should the bonds be reconfigured?
 - **Answer:** Keep the storage bonds. We need that bandwidth. I believe tsys6,7 have six ethernet ports each? Two on a riser card, and a four port add-on? Or maybe its four total? If four total, the 2 for storage, one for mgmt non rackrental, one trunked to rackrental would be how I want to go.
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
@@ -1,60 +0,0 @@
 # questions-v2.md
 > Git-tracked question log. The agent writes; the human reviews/edits inline.
 > Version up when a round of answers lands. Synthesize resolved Q&A to Discourse/Redmine.
 > See BASELINE-PROMPT.md §9.
 ## Resolved (from v1)
 ### Q1. Git remote for meta? — RESOLVED
 - **Decision:** New Gitea repo under TSYSGroupCorporate org: `TSYSGroupAIOS`. Template repo. Created and pushed.
 - **Synthesized to:** Meta repo created, `tea` + `docker login` noted as available on workstations.
 ### Q2. The bin/ wrapper gap — RESOLVED
 - **Decision:** No bin/ wrappers. Invoke real containers with `docker run --env-file`.
 - **Synthesized to:** PFVCluster AGENTS.md §CLI access; meta AGENTS.md §CLI invocation.
 ### Q3. Discourse pointer-header pattern — RESOLVED
 - **Decision:** Mandatory for ALL projects. No exceptions. Discourse/Redmine required.
 - **Synthesized to:** Meta AGENTS.md, check-rules.sh enforces.
 ### Q4. Sub-agent nudge hook — RESOLVED
 - **Decision:** No harness-specific hooks. Move to portable git hooks + AGENTS.md protocols. User shifting away from Crush to OpenWebUI/Hermes.
 - **Synthesized to:** All hooks ported to git hooks. No Crush-specific dependencies.
 ### Q5. JOURNAL.md vs Discourse — RESOLVED
 - **Decision:** No more JOURNAL.md. Redmine is SoR for work. Discourse for synthesized knowledge.
 - **Synthesized to:** Meta AGENTS.md, PFVCluster AGENTS.md.
 ### Q6. RackRental split-network design — RESOLVED
 - **Decision:** Keep storage bonds. If 4 NICs total: 2 storage, 1 mgmt non-RackRental, 1 trunked to RackRental VLAN 2.
 - **Synthesized to:** #433 (trunk ports), #432 (VLAN config).
 ## Open questions
 ### Q7. Close #167 (Small UPS Units Re-build)?
 - **Context:** #167 is an old (Dec 2024) vague ticket about rebuilding garage UPS units. It's been superseded by #372 (Tripp Lite physical reseat) and #439 (UPS data integration). Dates are stale (Aug 2025).
 - **Question:** Should we close #167 as superseded?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 ### Q8. Friday onsite work order?
 - **Context:** Friday 2026-08-14 onsite batch. Tickets: #341 (TEMPer deploy), #372 (Tripp Lite UPS reseat), #431 (Cisco fan replacement), #414 (tsys5 nic2 cable swap), #374 (PDU outlet renaming), #439 (UPS integration).
 - **Question:** What order do you want to tackle these? Cisco fan (#431) blocks #432/#433/#434/#436 — should it go first? TEMPer is the "fun" project — save for last?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 ### Q9. Session-start gate: relax for continuation sessions?
 - **Context:** You mentioned last session wanting to discuss relaxing the ticket gate for handoff/continuation sessions. The scope-alignment gate now handles this (presents handoff priorities, waits for user to name target). Is this sufficient, or do you want further changes?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
 ### Q10. Git flow: direct-push vs PR workflow (TSYSGroupAIOS conflict)?
 - **Context:** Template says "once work leaves the workstation, it goes through a PR" (tea CLI). This project's policy is ALWAYS commit+push directly to origin/main. Founder's own rule, reinforced all session.
 - **Question:** Keep direct-push for PFVCluster (ops repo, solo operator), adopt PRs for playbook code post-IaC-transition, or hybrid?
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —