codemap v0.1.2

• Fixes from the 17 Oct retest (round 8):
  • find_usages counts functions called by bare name in Vue templates ({{ formatMyr(x) }}), which in Nuxt are auto-imported helpers; such a helper is no longer reported unused.
  • A JS constant or function used only inside its own file counts those uses (same file) and is no longer reported unused.
  • The send result names the AI app (recorded when it connects), and an added comment on an existing issue says so: a short "seen again" note with this build's answer, not the whole issue again.
• Fixes from the 17 Oct retest (round 6):
  • codemap reports --send refuses a closed report, and checks the report on the current build first: if its check passes or its example no longer reproduces, the report is closed as fixed and nothing is sent.
  • The issue names the build the example was checked on just now, with that build's answer, plus "first seen on" the build it was reported on.
  • A report closed because its example no longer reproduces records that ("does not reproduce (reproduced on …)") with the new answer; the list shows a closed report's example as "reproduced on …".
• Fixes from the 17 Oct retest (round 4):
  • Test commands never include a base test class (abstract, or without test methods), which made PHPUnit run nothing; the tests that extend it are run instead.
  • A brief change summary that leaves out a long test list says so (tests_note).
• Fixes from the 17 Oct retest (round 3):
  • Change impact links tests that call a route with $this->call('POST', '/uri', …) or $this->json('PATCH', '/uri'), and requests after set-up calls ($this->actingAs($u)->postJson(…), withHeaders(…)->post(…)).
  • Change impact links tests that run a console command ($this->artisan('name'), Artisan::call('name')) to the command's class, so a change to anything the command uses lists them.
  • The development version stamp follows every commit (it watched only HEAD).
• Fixes from the 17 Oct retest (round 2):
  • find_usages follows services resolved from the container: app(X::class), resolve(X::class), App::make(X::class), app()->make(…), $this->app->make(…), chained or assigned to a variable first.
  • Live-data tests: browser tests of a page opened from a file (file://) or written with setContent are skipped.
• Fixes from the 17 Oct retest:
  • Release steps: static Nuxt apps (nuxt generate, ssr: false, a static preset) get generate and "deploy .output/public" instead of a Node server restart; Next.js output: 'export' too. Laravel + Vite cites only files the bundler reads.
  • Live-data tests: text the test typed or sent itself, negated checks, sentences, text patterns and text from the app's own code or translations no longer count.
  • Made-up examples: everyday words (save, phone, error) pass; only the project's compound names and its own name are blocked.
  • Resending a report for the same answer updates it instead of counting a repeat, and replaces the evidence.
  • The send result names the AI app when it does not offer question forms, with the terminal command first.
  • Development builds report <version>-dev+<commit>; release builds (and a checkout of the release tag) report the plain version.
• Wrong-answer reports: an 11th tool, report_wrong_answer, records an answer codemap got wrong (every answer now has meta.call_id). codemap also records contradictions, tool failures and slow answers on its own. codemap reports lists, re-checks, exports, closes and clears them. A report with a made-up example that reproduces (checked to hold nothing from the real project) can be sent as a GitHub issue after the person agrees.
• Release check: release_steps, the server steps a release needs (installs, migrations, caches, queue and server restarts, rebuilds, new environment variables), worked out from what changed.
• Project rules tied to files ([[rules]] in .codemap.toml), returned by the release check and by change impact when a matching file changes.
• Leftover mentions: names deleted or renamed on the branch that code, tests, comments or docs still use.
• Tests that depend on live data: browser and PHP tests that check data they never create.
• New type errors only: verify with type_errors (the type check's output) reports only errors not in the saved starting point.