Skip to content

v1.6.0 — Naming and truncation fixes

Choose a tag to compare

@TylerIlunga TylerIlunga released this 20 Aug 03:00
60f6b54

Naming and truncation fixes

Fourth pass, targeting Server Coherence complaints not covered by the prior three releases.

  • HTTP-verb-style names. Three tools carried a bare HTTP-method word as their OAS summary ("POST Company Role"), producing tool names like post_company_role/patch_company_role. Normalized to natural verbs at the source.
  • Cross-version sibling pairing. Filler articles ("a", "an", "the") no longer cause two names for the same operation to miss each other during version-sibling grouping.
  • All 6 remaining opaque numeric-suffix names fixed (create_timecard_entry_project_2, list_project_tools_2, ...) — the collision resolver now catches cascading renames instead of falling back to a bare digit, and a scopeless sibling in a scope-spanning family gets an explicit _unscoped label.
  • Multipart upload boilerplate removed from file-upload PATCH/PUT tools — they were incorrectly told to "send only the fields you intend to change."
  • Description truncation fixed — two independent truncation limits were fighting each other and severing a markdown file-format table mid-row on a schedule-file upload tool; both are now aligned, and the sentence-boundary rollback no longer mistakes an abbreviation ("e.g.") for the end of a sentence.

No breaking changes to tool names beyond the 3 HTTP-verb renames (post_company_rolecreate_company_role, patch_company_roleupdate_company_role) and the 6 numeric-suffix renames listed above.