During contract-seam scanning across CDH repos, I found a route-shape mismatch risk across TinyNode consumers.nn- deer uses /app/create, /app/query, /app/update, /app/overwriten- TPEN-services appears to use root routes /create, /query, /update, /overwrite, /deletennRecommended adjustment:n1. Document canonical TinyNode API surface and supported aliases.n2. Publish OpenAPI for TinyNode routes (including /app/* and root aliases if both are supported).n3. Add compatibility tests ensuring both consumer patterns continue to work, or explicitly deprecate one pattern with migration guidance.nnWhy this matters:n- Divergent route prefixes/method expectations increase break risk across consumers.n`nFiled by automation as requested; label: copilot.
During contract-seam scanning across CDH repos, I found a route-shape mismatch risk across TinyNode consumers.
nn- deer uses /app/create, /app/query, /app/update, /app/overwriten- TPEN-services appears to use root routes /create, /query, /update, /overwrite, /deletennRecommended adjustment:n1. Document canonical TinyNode API surface and supported aliases.n2. Publish OpenAPI for TinyNode routes (including /app/* and root aliases if both are supported).n3. Add compatibility tests ensuring both consumer patterns continue to work, or explicitly deprecate one pattern with migration guidance.nnWhy this matters:n- Divergent route prefixes/method expectations increase break risk across consumers.n`nFiled by automation as requested; label: copilot.