Skip to content

fix: render one-month record ages#41

Merged
Deepam02 merged 2 commits into
agentctxhq:mainfrom
MFA-G:fix-format-age-one-month
Jun 25, 2026
Merged

fix: render one-month record ages#41
Deepam02 merged 2 commits into
agentctxhq:mainfrom
MFA-G:fix-format-age-one-month

Conversation

@MFA-G

@MFA-G MFA-G commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • roll age formatting from days to months at 30 days instead of 60
  • add MCP search coverage for a 30-day-old record rendering as 1mo

Closes #37

Validation

  • npm run test --workspace packages/agentctx -- test/mcp/tools.test.ts
  • npm run typecheck --workspace packages/agentctx
  • npm run lint

@Deepam02

Copy link
Copy Markdown
Contributor

Hi @MFA-G
Please rebase and resolve the merge conflicts.

@MFA-G
MFA-G force-pushed the fix-format-age-one-month branch from 242abfe to 1e9029d Compare June 15, 2026 13:29
@MFA-G

MFA-G commented Jun 21, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @Deepam02 — I've merged the latest upstream/main into this branch to resolve the conflicts. The merge was clean (auto-merge handled tools.ts and tools.test.ts), and the full suite passes locally: npm run typecheck, npm run lint (biome, 92 files clean), and npm run test (298 tests, all green). The one-line formatAge fix and its regression test are intact. Ready for another look.

@Deepam02
Deepam02 merged commit d333a49 into agentctxhq:main Jun 25, 2026
4 checks passed
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.

formatAge never renders "1mo" — months bucket starts at "2mo" (days < 60)

2 participants