fix(share): expose owner-scoped persisted stop tasks

This commit is contained in:
a1chzt
2026-10-10 12:18:31 +08:00
parent 973e8e2c25
commit 76bac57bd9
4 changed files with 131 additions and 6 deletions
+11
View File
@@ -30,6 +30,17 @@ export interface PublicFileStopRetryRequest {
slug: string;
}
/** A persisted pending stop visible only to its current verified owner. */
export interface PublicFileStopListItem extends PublicFileStopRetryRequest {
/** Eligible for the existing automatic retry budget, not proof of a running stop. */
retrying: boolean;
}
/** GET /api/public-file-stops; includes exhausted tasks until confirmed stopped. */
export interface PublicFileStopListResponse {
tasks: ReadonlyArray<PublicFileStopListItem>;
}
export interface PublicFileStopRetryResponse extends PublicFileStopRetryRequest {
status: 'stopped';
}
+4 -5
View File
@@ -822,11 +822,10 @@ export interface ProjectCommentReadRequest {
*
* ## Exactly once
*
* This is delivered on the delete response and nowhere else. The project is
* gone, so there is no row left to hang a persistent indicator on, and no
* later request will rediscover the condition. A surface that drops it drops
* it permanently — which is why it rides the response every consumer already
* reads rather than a separate channel one of them might not subscribe to.
* The deletion response is delivered once. The current verified owner can
* rediscover persisted pending stops after reload via GET /api/public-file-stops,
* even when the project is gone. That list includes exhausted tasks, but does
* not replay the deletion response or its diagnostic code.
*/
export interface ProjectDeleteShareResidual {
/**