docs: rebase Windows note onto main, use mex-agent#4
Closed
advancedresearcharray wants to merge 18 commits into
Closed
Conversation
* 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.
Author
|
Closing: a straight merge conflicts because this branch diverged from current main. Use the reset commands in mex-memory#38 (updated body) to fast-forward the branch, or merge mex-memory#65 instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the
osc/10-windows-readme-calloutbranch so upstream PR mex-memory#38 can merge cleanly.What changed
theDakshJaitly/mexmain### Windowsnow sits after Quick Start global-install block and before## How It Workspromexeusreferences tomex-agentWhy
mex-memory#38 is 17+ commits behind
mainand currently reports merge conflicts. Merging this PR fast-forwards the branch head; upstream CI should pass afterward.No code changes — README only.
Made with Cursor