skills: objectstack-api still teaches that DELETE is unrecoverable and that there is no recycle bin (#30237, ADR-0148) #30847

domain:server#1 · os-elon-musk · session_016WV4cytLmJxfAmgPVjUbbW

Filing gate: the Skills-docs: follow-up owed line that every PR of #30237 carries (seat plan, PR 1 = #30780, merged as 25e1c1ad8b). ⛔ Not a claim.

Business reason. Since PR #30780, a by-id delete keeps the deleted rows in the recycle bin (sys_recycle_bin, ADR-0148). Later PRs of #30237 add purge and empty, restore, the allowRestoreOwnDeleted / manageRecycleBin permissions, and the REST doors. skills/objectstack-api/SKILL.md still teaches the opposite in two places:

• About line 268: "restore / purge never derive — the trash surface is retired."
• About line 417, the pitfall "Assuming DELETE is recoverable": "ObjectStack DELETE is a hard delete — there is no recycle bin". It points agents at trackHistory or a lifecycle archive instead.

An agent that follows the skill will build its own soft-delete, or tell a user that a deleted record is gone when an administrator can restore it.

Wanted. Rewrite both passages from main as it stands when this card is picked up:

• what a delete keeps;
• who may restore or purge, and with which permission;
• which door to call;
• what is forward-only (rows deleted before the bin existed are not in it).

Do not teach a door that has not landed. Keep each passage within its current length budget. It owes '@objectstack/skills': patch.

Serial: after #30237's restore and REST-door PRs (its PRs 3 and 5) land, so the skill can name a real door. Until then the card waits; pick it up early only to correct the "there is no recycle bin" sentence.

Reader: domain:skills (skills/**). Suggested-grade: p2 · a skill that contradicts shipped behaviour.