feat(api): support binding release

[onutc]

Summary

• add internal binding delete endpoints so deployments can fully release route claims
• cover create/fetch/delete binding lifecycle in API tests
• keep the earlier workspace-release architecture docs in the same PR

Validation

• go test .
• npx -y @simpledoc/simpledoc check

[gitrank-connector]

👍 GitRank PR Analysis

Score: 20 points

Metric	Value
Component	Other (1× multiplier)
Severity	P2 - Medium (20 base pts)
Final Score	20 × 1 = 20

Eligibility Checks

Check	Status
Issue/Bug Fix	❌
Fix Implementation	✅
PR Documented	✅
Tests	✅
Lines Within Limit	✅

Impact Summary

This PR adds support for releasing route claims by implementing DELETE endpoints for internal bindings, completing the create/fetch/delete lifecycle. The implementation includes proper HTTP status handling (204 NoContent for success, 404 for missing bindings, 500 for errors) and comprehensive test coverage. Documentation is updated to clarify that disconnect/uninstall should release active claims rather than maintain disconnected reservations.

Analysis Details

Component Classification: This PR adds a new DELETE endpoint for internal bindings, which is an API feature addition that doesn't fit neatly into a specific domain category. It's categorized as OTHER since no domain-specific component multiplier applies.

Severity Justification: This is a P2 (Medium) severity contribution. It implements a functional feature (binding deletion) that completes a lifecycle operation, but it's not critical infrastructure and has a workaround (manual cleanup). The feature enables proper resource cleanup for deployments but doesn't address a security risk or service outage.

Eligibility Notes: Tests are required and included: TestInternalDeleteBindingRemovesStoredBinding validates the full lifecycle (PUT create, DELETE remove, GET verify 404). The PR is well-documented with clear summary of changes and validation steps. This is a new API feature (not a bug fix), so issue=false. fix_implementation=true because the code correctly implements the DELETE handler with proper error handling. pr_linked=true due to meaningful description and validation section.

---

Analyzed by GitRank 🤖