dx/test: mcp add --header-command flag, tui-migrate tests, golden upgrade fixture

Open
#1,000 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Locate the altimate mcp add entry point, tui-migrate.ts, and the existing migration or golden-test setup. Start by tracing the existing --header handling and how tui-migrate.ts reports failures, then inspect the 0.8.10 opencode.json and opencode-local.db fixture inputs. Done means header-command support, dedicated migration coverage, and a 0.8.10-to-0.9.1 parity test for session, config, and theme data.

Written by the indexing model from the issue text.

Description

Found during v0.9.1 release review (Data-Engineer). Deferred DX/test debt: (1) altimate mcp add has no --header-command flag (parity with --header) — users must hand-edit JSON for bearer-auth. (2) tui-migrate.ts (extracts theme/keybinds/tui → tui.json) has no dedicated tests; a silently-failed migration drops customizations without error. (3) No end-to-end golden-fixture upgrade test loading a real 0.8.10 opencode.json + opencode-local.db and asserting session/config/theme parity on 0.9.1.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.