Agent Instructions

This workspace currently documents lab infrastructure access. Keep changes focused, readable, and safe for operators who may use these notes during cluster work.

Repository Map

Working Rules

• Prefer concise Markdown with tables for cluster inventories and command examples for operational steps.
• Keep dates explicit in YYYY-MM-DD format when recording verification or decisions.
• Update CHANGELOG.md for every meaningful change to tracked files. This is mandatory.
• Changelog entries must include intent, touched files, verification, deployment impact, and security notes when relevant.
• Keep the newest changelog entry first.
• Update MEMORY.md whenever durable project context changes, such as repo URLs, deployment setup, cluster access patterns, bootstrap steps, or long-lived operating conventions.
• Do not commit or paste kubeconfig contents, tokens, client certificates, private keys, or passwords.
• Treat commands against clusters as potentially sensitive. Prefer read-only verification commands unless the user explicitly asks for changes.
• When verifying OpenShift access, use ssh ze@dl385, ocpctx <cluster>, and oc commands.
• When verifying RKE2 access, use kubectl --kubeconfig ~/.kube/configs/<cluster>.kubeconfig.
• Restore or clear KUBECONFIG after verification when practical:

unset KUBECONFIG

Documentation Style

• Use root-level docs unless the workspace grows enough to justify a docs/ tree.
• Link related docs by filename.
• Keep secrets out of examples; show paths and command shapes only.
• If cluster access is rechecked, update INFRASTRUCTURE.md and note the new verification date.
• If the wiki navigation changes, update scripts/build-wiki.mjs, README.md, CHANGELOG.md, and MEMORY.md together.