[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"journal-post-sm-user-plugin-0-1-14":3},{"author":4,"categories":8,"content":13,"content_html":14,"created_at":15,"excerpt":16,"featured_image_url":13,"featured_images":17,"id":18,"is_pinned":19,"metadata":13,"next_post":20,"previous_post":24,"published":28,"published_at":29,"reading_time":6,"related_posts":30,"slug":31,"sources":13,"tags":32,"title":33,"translations":13,"updated_at":34},{"first_name":5,"id":6,"last_name":5,"login":7},"",1,"jakubzych@gmail.com",[9],{"id":10,"name":11,"slug":12},3,"Plugins","plugins",null,"\u003Ch2>Fixed\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>When an MCP session was opened with a personal \u003Ccode>usr_\u003C\u002Fcode> token, the dispatch credential now carries that token's id, so a route running under MCP dispatch can record which token made a change. An OAuth session's credential keeps id 0. The credential is still never saved.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Requires SummerCMS v0.5.0.\u003C\u002Fp>\n","2026-10-28T22:31:19+00:00","The MCP dispatch credential carries the personal token id.",[],48,false,{"id":21,"slug":22,"title":23},53,"sm-seo-plugin-0-1-0","sm-seo-plugin 0.1.0",{"id":25,"slug":26,"title":27},49,"sm-user-plugin-0-1-15","sm-user-plugin 0.1.15",true,"2026-10-28T10:40:16+00:00",[],"sm-user-plugin-0-1-14",[],"sm-user-plugin 0.1.14","2026-10-29T10:39:23+00:00"]