Memtrace v1.0.4

Memtrace v1.0.4

API handler linkage stops counting database tables as routes

Fixed

• A busy sidecar is no longer mistaken for a missing one on small requests. The time allowed for an answer grew with the number of documents, but the wait to be served does not — it depends on how busy the sidecar is. A request covering only a few documents was therefore given the least time exactly when the sidecar was most loaded, and the view reported the sidecar as not running while it was simply working.
• Decision records load again, and fast. The sweep that finds a project's governance documents was walking into the throwaway copies of the repository that coding agents create for themselves, and treating every markdown file inside them as a governance document. On this project that turned a handful of real documents into nearly two thousand, and sixteen megabytes was sent to the decision sidecar every time the view opened — so it timed out and showed nothing. Those agent copies are now skipped.
• The API handler linkage score no longer counts database tables as web routes. Every table in a database migration was being treated as a code-registered HTTP route, and since a table cannot have a request handler, each one counted against the score. On this project that was 86 of the 93 routes reported as unlinked, reporting the worst possible grade for a codebase whose actual route linkage is good. The score now covers only things that can genuinely have a handler, and anything new has to be explicitly included rather than counted by default.

Install

npm install -g memtrace