The OpenAPI document describes the feed and the inbox: feed, chips, asks, bulk decide and their undo #5156

Intent: a harness can read the owner's feed and clear the inbox through the OpenAPI document alone.

Done:

• [ ] src/contract/openapi.ts has rows for every route feedRoutes registers in src/http/feed.ts (GET /api/v1/feed, GET and POST /api/v1/feed/chips, GET /api/v1/asks, POST /api/v1/asks/bulk, /api/v1/asks/bulk/{id}/undo, /api/v1/asks/decide, /api/v1/asks/decide/{id}/undo, /api/v1/asks/proposal/{id}/{verb}). Each has auth, the token scope acting needs, body and query fields as its handler reads them, its success status, and its refusals by stable error code. The bulk rows say that the default is a preview
• [ ] Placed as one block directly after the /api/v1/returns row, changing no other row
• [ ] test/openapi.test.ts's every described route is registered reads src/http/feed.ts as well, so these rows pass it
• [ ] A new test asserts each new path and method is in the served document