feat(api): embed pending collaborator invites on the owner's own tracks

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code

[raymondjacobson]

Backend for the apps edit-form fix: an owner editing a track was dropping still-pending collaborator invites, because the edit form seeds its collaborators field from the track response — which only carried accepted collaborators. On save, the ETL reconciles the metadata set and removes any invite not present, so pending ones vanished.

Change

• GetTrackCollaborators now returns accepted and pending rows (with status). The embed splits them:
  • collaborators — accepted, on every track response (unchanged behavior).
  • pending_collaborators — new, populated only on the requester's own tracks.
• Owner-scoped: pending user IDs are resolved and embedded only where owner == my_id, so pending invites never surface to other viewers. (They're public on-chain regardless, but there's no reason to hand them to everyone.)
• swagger: pending_collaborators declared on the track schemas.

Follow-up (apps)

The edit form will initialize from collaborators + pending_collaborators so saving preserves pending invites. Needs an SDK regen once this deploys (the field reproduces cleanly, same as collaborators).

Tests

TestPendingCollaboratorsVisibleToOwnerOnly: owner sees the pending invite; a non-owner sees only the accepted collaborator. Existing collaborator/embed/profile suites still pass.

Perf

Same bounded, index-served embed query as before (PK leads on track_id, ANY(@ids)); it now also returns pending rows, post-filtered by the same index. No new round-trips.

🤖 Generated with Claude Code