Skip to content

docs: rebase Windows note onto main, use mex-agent#1

Closed
advancedresearcharray wants to merge 18 commits into
mvanhorn:osc/10-windows-readme-calloutfrom
advancedresearcharray:osc/10-windows-readme-callout
Closed

docs: rebase Windows note onto main, use mex-agent#1
advancedresearcharray wants to merge 18 commits into
mvanhorn:osc/10-windows-readme-calloutfrom
advancedresearcharray:osc/10-windows-readme-callout

Conversation

@advancedresearcharray

Copy link
Copy Markdown

Rebases the Windows/WSL README callout from mex-memory#38 onto current upstream main and updates promexeus references to mex-agent.

This is intended to update the head branch for mex-memory#38 so it can merge cleanly.

Changes:

  • Rebased onto upstream main (was 17 commits behind)
  • Resolved README conflict: Windows subsection now sits after Quick Start, before How It Works
  • Replaced outdated npx promexeus / npm install -g promexeus with mex-agent to match current README

Made with Cursor

theDakshJaitly and others added 18 commits May 14, 2026 06:55
* feat: add operational memory commands

* feat: add interactive terminal dashboard

* feat: polish terminal dashboard

* fix: use setup banner in tui

* style: lighten tui banner

* style: restore tui wordmark

* chore: prepare v0.3 release

* ci: drop unsupported node 18 check

* fix: address release review feedback
…ex-agent (mex-memory#44)

* export field configured

* cleanups done, inclding rewriting package-lock.json
…x-memory#45)

* feat: compatibility contract, trace field, git-install ergonomics

* LogOpts inside both export and import field
…mex-memory#47)

Per mex-memory#43, mex log and mex timeline have direct module tests in
test/events.test.ts but no Commander-level coverage. The risky areas
called out in the Copilot review on mex-memory#39 (invalid --type, repeated --file
accumulator, --limit parsing through parsePositiveIntArg, parseAsync
wiring) had no regression net.

This PR adds test/cli.test.ts covering:

- parsePositiveIntArg + parseIntArg direct tests for positive / zero /
  negative / non-numeric inputs.
- mex log via parseAsync: default --type=note, repeated --file
  accumulates, --type decision propagates, invalid --type is rejected at
  the handler layer.
- mex timeline via parseAsync: --limit parses as integer, --limit 0 and
  --limit foo throw, --json / --since / --type flags propagate.

Each Commander test rebuilds the command locally rather than importing
program from src/cli.ts (which calls program.parse() at import time).
src/cli.ts exports parsePositiveIntArg and parseIntArg so the parser
helpers can be tested directly.

patterns/cli-option-parsing-tests.md captures the approach per the
AGENTS.md After Every Task rule.

Fixes mex-memory#43

Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
Co-authored-by: Daksh Jaitly <thedakshjaitly@gmail.com>
…or CLI

- CONTRIBUTING: add 'Adding a drift checker' section (checker shapes, the
  closed IssueCode union, registration in src/drift/index.ts, tests) plus a
  good-first-issue pointer, to support the contributor issues opened from
  the task list.
- bug_report template: replace the stock browser/smartphone fields with
  CLI-relevant ones (mex --version, node version, OS, install method,
  command output / mex check --json).
mex --version was hard-coded to "0.3.5" in src/cli.ts while package.json had
advanced to 0.5.0. Read the version from package.json at runtime (new
src/version.ts) so it can never drift again, and add a regression test
asserting the program's configured version matches package.json.

Closes mex-memory#48
Implements the todo-fixme checker (warning per marker with file and line),
registers it in drift detection, and updates README/CONTRIBUTING/CHANGELOG
so checker counts match the 10 modules in src/drift/checkers/.

Closes mex-memory#54 and mex-memory#49.

Co-authored-by: advancedresearcharray <advancedresearcharray@users.noreply.github.com>
Adds a broken-link drift checker that flags Markdown links to local files that do not exist. Closes mex-memory#52.
Adds a short Windows subsection that:
- points users at `npx promexeus setup` as the friction-free path
- warns against mixing WSL + native Windows when using `setup.sh`
- links back to issue mex-memory#10 for context

Documents the mitigation the maintainer described in the issue thread
(npx path sidesteps it completely).

No code changes.
@advancedresearcharray

Copy link
Copy Markdown
Author

Closing: diverged history makes a merge PR impractical. The rebased branch is at advancedresearcharray:osc/10-windows-readme-callout instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants