You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem\n\nThe MCP tool supports two output types: (default) and . When using , the returned JSON object should include per-word breakdown with , , , and for each matched word.\n\nThis is documented in and implemented in 's , but the MCP server in does not include in its timestamp output.\n\nCurrent MCP timestamp output:\n\n\nExpected (per docs and CLI):\n\n\n## Scope\n\n1. Add field to the timestamp output branch in in .\n2. Update to assert is present and correctly structured for timestamp output.\n3. No changes needed to — it already describes the correct output.\n\n## Acceptance\n\n- returns a array with per-word , , , and .\n- Existing tests pass and new assertions hold.
Problem\n\nThe MCP tool supports two output types: (default) and . When using , the returned JSON object should include per-word breakdown with , , , and for each matched word.\n\nThis is documented in and implemented in 's , but the MCP server in does not include in its timestamp output.\n\nCurrent MCP timestamp output:\n\n\nExpected (per docs and CLI):\n\n\n## Scope\n\n1. Add field to the timestamp output branch in in .\n2. Update to assert is present and correctly structured for timestamp output.\n3. No changes needed to — it already describes the correct output.\n\n## Acceptance\n\n- returns a array with per-word , , , and .\n- Existing tests pass and new assertions hold.