Add test coverage documenting DELETE /api/v1/anchors/:id idempotent-deactivate behavior

[Jagadeeshftw]

📌 Description

DELETE /api/v1/anchors/:id deactivates an anchor per the README, but the response for deactivating an already-inactive anchor isn't documented or (as far as can be told) explicitly tested — is a second call a no-op 200, or does it error? DELETE-style operations are conventionally expected to be idempotent, and callers (including the frontend's confirm-dialog-guarded deactivate action) need a defined contract.

🧩 Requirements and context

• Add a test asserting the actual current behavior of calling DELETE /api/v1/anchors/:id twice in a row.
• If the current behavior isn't idempotent (e.g. errors on the second call), evaluate whether to make it idempotent (200/no-op) for consistency with REST conventions — implement whichever is decided and document it.
• Document the decided contract in the README next to the endpoint description.

🛠️ Suggested execution

• Add the double-call test to src/routes/anchors.test.ts.
• If a behavior change is warranted, update AnchorService/AnchorRepository accordingly.
• Update the README's Anchors section with the explicit contract.

✅ Acceptance criteria

• Repeat-deactivate behavior is explicitly tested.
• Behavior matches the documented contract.
• README updated with the explicit contract.

🔒 Security notes

No new attack surface; clarifies an operation already gated by an existing auth/validation path.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[GBOYEE]

Hello! I'd love to pick this one up (Add test coverage documenting DELETE /api/v1/anchors/:id idempotent...). I'll implement the helper and integrate it. Happy to coordinate if anyone's already looking at it.

[Jagadeeshftw]

@GBOYEE thanks for the interest — you're currently at the 6 open-issue assignment cap for this repo, so I can't assign this one right now (backfill automation). Please finish or release one of your existing assigned issues, then request this one again and it'll be picked up.

[grantfox-oss]

🦊 GrantFox — @GBOYEE has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #97)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.