Files
mcode-sl/CURRENT_STATE.md
T
aygea fd8e8cbbd7 docs: AGENTS.md + evidence-backed scaffold (state, trials, decisions, handoff)
- AGENTS.md operating rules incl. Gitea SSH port-2222 note + known_hosts incident
- CURRENT_STATE / TODO / CHANGELOG / TRIALS
- trials: endpoint-key pairing; config-merge safety matrix 14/14 (verify.sh + output)
- docs: DECISIONS (mcode 0.6.12 bundle facts, digest-pinned), FEATURE-MATRIX, PROJECT-HANDOFF
- handoffs: TEMPLATE + 2026-10-19 initial-install record
2026-10-19 23:25:21 -07:00

2.0 KiB
Raw Blame History

CURRENT_STATE

Updated: 2026-10-19

Objective

Self-contained, secret-safe z.ai GLM 5h-usage segment for the MiniMax Code statusline, installable on 1 macOS + 2 Ubuntu systems with one curl | bash line.

Verified capabilities (this machine, mcode 0.6.12, Ubuntu-based PVE host)

  • confirmed — Segment renders real quota data: 🔥 1% · 4:16a(4h59m) right after install (cache primed through SecretVault key against https://api.z.ai).
  • confirmed — Config merge safety matrix 14/14 (trials/config-merge-safety-2026-10-19/output.txt): atomic write, 0600 on new files, backup equals pre-merge original, duplicate-structure refusal, provider untouched, piped-install embed identical, clean uninstall.
  • confirmed — Vault key pairs with api.z.ai (200); old credential.json clientKey pairs with the vault.itsaygea.com proxy (200); vault key against the proxy → 401. (trials/mcode-endpoint-key-pairing-2026-10-19/record.md)
  • confirmed — mcode statusline mechanics for 0.6.12: tui.statusLine + tui.customStatusLine in ~/.minimax/config.yaml; JSON on stdin; stdout becomes the custom-command item on exit 0; colorMode: ansi passes ANSI through; intervalSeconds ≥10, timeoutMs 500–30000. Evidence: bundle reads in docs/DECISIONS.md (release digests recorded).
  • confirmed — Pushed to git@git.itsaygea.com:admin/mcode-sl.git (port 2222 SSH).

Active work

None in flight. Last stage (initial install + push) completed 2026-10-19.

Blockers

  • Visual confirmation of the rendered segment in the live TUI requires the user to restart MiniMax Code. Until then, ANSI/emoji rendering in the statusline is inferred (config accepted by the parser; passthrough path verified in code, not on screen).

Exact next action

User restarts the MiniMax Code TUI and confirms the segment renders (colors, emoji, no misalignment). Then roll out to the two Ubuntu machines + macOS via the curl one-liner and record results in TODO.md / docs/FEATURE-MATRIX.md.