Files

3.8 KiB
Raw Permalink Blame History

MEMORY.md

Long-term curated memory for Shard.

  • 2026-02-21: Identity initialized as Shard ✨
  • Human: Jason (Dingo)
  • Telegram sender ID for Jason: 8538271745
  • 2026-03-10: Autonomy policy baseline established (safe memory, approvals for questionable actions, audit+rollback logging).
  • 2026-03-10: Primary active project focus is SOR.
  • 2026-03-10: Nextcloud collaboration workspace deployed at cloud.aeternalisgames.com on Kubernetes with HTTPS, external PostgreSQL, and Redis.
  • 2026-03-10: Nextcloud collaboration stack prepared with shard user, Talk app enabled, and Google OIDC social login provider staged for validation.
  • 2026-03-11: Infrastructure capability confirmed — shard access on barn validated for libvirt VM listing/creation workflows.
  • 2026-03-19: SOR backend reached a durable schema milestone: canonical AbilitiesJson model with compatibility fallback for legacy EffectsJson, plus migration path; subsequent server fix enforced CanMove/CanUseAbility suppression during lock states.
  • 2026-03-25: Nextcloud Notes sync now requires the server-side notes app to be installed/enabled (validated with Notes 4.13.1).
  • 2026-03-25: Prime OAuth on shard-host was repaired and validated; auth flow is healthy again.
  • 2026-03-27: SOR ability-system expansion reached a major milestone: Phases 1-3 (new trigger/condition/filter/effect primitives plus AbilityBuilder support) landed and were build-validated across SOR.Game, SOR.Admin, and client Godot HTML5 export (HEAD 8f0ed9d).
  • 2026-03-28: SOR targeting semantics were materially hardened at 2e3e284 (multi-target, UpTo, ChooseOne, LinearOnly, and line-of-sight legality/resolution gaps fixed), establishing a more reliable baseline for authored-card targeting behavior.
  • 2026-03-29: SOR browser touch-input contract advanced to 206ff9a via a focused interaction pass (protect one-finger orbit from touch/mouse gesture conflicts, preserve two-finger pan + pinch zoom, and add tap/hold selection affordances), setting up on-device UX validation as the next execution gate.
  • 2026-03-30: SOR touch UX received a follow-up stabilization at 6e27f57 (tap-suppression fix), reducing accidental tap-trigger behavior after touch gestures and improving reliability of the browser/mobile interaction contract.
  • 2026-04-01: Keycloak was deployed as centralized identity at auth.aeternalisgames.com (namespace keycloak) with external Postgres, realm aeternalis, and baseline platform role groups established.
  • 2026-04-01: External Gitea SSH access was enabled via gitea-ssh-public LoadBalancer (172.10.1.201:22), creating a durable direct-SSH ingress path for repository operations.
  • 2026-04-02: SOR integrated Keycloak login via Authorization Code + PKCE (d5363fa), and realm default-group hygiene was tightened so new users default to /player only.
  • 2026-04-03: IAM/RBAC hardening expanded in realm aeternalis with app-scoped groups and enforcement across Argo CD, Gitea, and Nextcloud (group-gated access paths for staff/player segmentation).
  • 2026-04-03: SOR auth reliability advanced at cfb10ae with Keycloak audience-validation and packet-drain race fixes, setting up end-to-end login/reconnect validation as the next execution gate.
  • 2026-04-04: SOR admin auth hardening progressed to e4ddd80, persisting DataProtection keys in Redis to prevent cross-pod cookie decryption failures in multi-pod deployments.
  • 2026-04-04: Platform IAM posture tightened with Argo CD default-deny RBAC (explicit /argo-admin + /argo-readonly grants only) and removal of local Argo user logins.
  • 2026-04-08: Critical infra lesson captured — new VMs (including Ceph/PostgreSQL roles) must use the storage pool, not host local primary disks (90–100GB). Prior local-disk placement filled hypervisor disks and caused VM pauses.