Harden TinyNode endpoint adapter to avoid route prefix drift

During interaction scanning, TPEN-services appears to call TinyNode CRUD routes with method/path conventions that may not match all other consumers (notably DEER using /app/*).`n`nSuggested adjustment in TPEN-services:`n1. Centralize TinyNode endpoint mapping in one adapter module.`n2. Explicitly version or configure route prefix (/app vs root).`n3. Add integration tests against TinyNode route contract.`n`nThis would reduce drift and make contract-seam checks easier to enforce.`n`nFiled by automation as requested; label: copilot.

Start by tracing interaction scanning in TPEN-services and comparing its TinyNode CRUD method/path conventions with the DEER consumer's /app/* routes. Review the proposed adapter boundary and route contract expectations, then add integration coverage showing consistent configurable or versioned prefixes. Done means endpoint mapping is centralized and the TinyNode route contract is enforced by tests.

Written by the indexing model from the issue text.