[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"journal-post-sm-user-plugin-0-1-15":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>Changed\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A 403 from \u003Ccode>user.scope:<scope>\u003C\u002Fcode> now includes \u003Ccode>missing_scope\u003C\u002Fcode>, and a 403 from \u003Ccode>user.permission:<code>\u003C\u002Fcode> includes \u003Ccode>missing_permission\u003C\u002Fcode>. The existing \u003Ccode>error\u003C\u002Fcode> and \u003Ccode>message\u003C\u002Fcode> fields are unchanged. A plain-HTTP script or personal-token client can now tell which scope or permission it lacks.\u003C\u002Fli>\n\u003Cli>The \u003Ccode>user_me\u003C\u002Fcode> MCP tool description says it needs scope \u003Ccode>read\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Requires SummerCMS v0.5.0.\u003C\u002Fp>\n","2026-10-28T22:31:20+00:00","403 responses name the missing scope or permission.",[],49,false,{"id":21,"slug":22,"title":23},48,"sm-user-plugin-0-1-14","sm-user-plugin 0.1.14",{"id":25,"slug":26,"title":27},46,"summercms-0-5-2","SummerCMS 0.5.2",true,"2026-10-28T13:06:20+00:00",[],"sm-user-plugin-0-1-15",[],"sm-user-plugin 0.1.15","2026-10-29T10:39:23+00:00"]