mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 04:36:40 +00:00
kevinveenbirkenbachandClaude Opus 5
5137465c6f
3529 invalid comments in 528 files, grandfathered in while the linter only saw the working-tree diff. Removal ran through the linter's own collectors, so detection and deletion cannot drift: a comment whose opener line is blank before it and whose closer line is blank after it loses all its lines, anything else loses only the comment region, and a line left holding a bare delimiter goes with it. Five files keep their comments behind a nocheck marker instead. Four are upstream configs whose inline docs are upstream's own (mautrix, systemd journald, nextcloud-oidc-login, MediaWiki). In littlejs the commented-out entries ARE the deactivation mechanism for an example tile, so deleting them would delete configuration. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Network 🌐
Contributor-side network tooling: probe the live container network stack, suggest free per-role subnets, and suggest free host-bound ports.
Subcommands 🧭
| Path | Purpose |
|---|---|
| diagnose/ | Run python -m cli.contributing.network.diagnose to print a structured DNS / TCP / TLS / PMTU report (IPv4 + IPv6) plus interface MTU, /etc/resolv.conf, /etc/hosts, proxy env vars, and CA bundle summaries from inside the running infinito container. Exposed as make diagnose-network. |
| address/ | cli contributing network address suggest: propose the next free per-role IPv4 subnet(s) gap-first within the established umbrella blocks. |
| ports/ | cli contributing network ports suggest: propose free host-bound ports inside PORT_BANDS.<scope>.<category>. |
Related Documentation 📚
- docs/contributing/actions/debugging/network.md explains how to read the diagnose output and how to fix MTU / IPv6 / connectivity issues.
- docs/contributing/tools/network/ covers the contract of the
addressandportssuggesters.