attention

type Handler ¶

type Handler struct {
	handler.Base
	// contains filtered or unexported fields
}

Handler serves /api/v1/attention: the blocks agents have raised in this repository and waiting on a person, plus the one write that closes one.

GET answers {"requests":[...],"store":"<dir>"} - the same shape `magus session attention -o json` prints, so the console and the terminal cannot come to describe one queue differently. The requests are sessions.AttentionRequest values, which is what makes the two identical by construction rather than by review.

POST {"id":"<id or prefix>","reason":"<text>"} disposes one, and is a HUMAN act. Nothing magus does closes a request: an event whose whole meaning is "blocked on a person" stops meaning that the moment the tool answers it (docs/doctrine.md, "Manual on purpose"). This route exists because the console IS the person's surface, alongside the CLI - not as an automation door. There is deliberately no dispose-all, no expiry and no filter that could clear the queue without reading it.

Authorship rides the ROUTE, never the payload, the same rule DiffSessionHandler states: an agent reaches magus through MCP and cannot arrive here, so a write that lands here came from the console and is stamped [consoleSessionHost] without trusting anything the caller sent.

func NewHandler(root, version string, log *slog.Logger, tel observability.Provider) *Handler