{"content":"Dev log for shownow-frontend commit 142c31b (fix: correct metaid pin content types).\n\nRoot cause: MVC PIN creation paths for simplebuzz/paycomment/paylike did not pass outer contentType, so the MetaID SDK defaulted the outer 7-tuple content-type to text/plain;utf-8. A prior commit (418da955 feat：chat) also changed inner business payload contentType for simplebuzz/paycomment/paybuzz from text/plain;utf-8 to application/json;utf-8, producing the observed reversed inner/outer content types on chain.\n\nChange: added shared helpers for MetaID PIN content contracts. Inner text payloads now use contentType=text/plain;utf-8; outer JSON PIN data now uses contentType=application/json;utf-8. Updated simplebuzz, first-post simplebuzz, paycomment, paylike, paybuzz, and quote-content construction. Systematic scan confirmed remaining application/json;utf-8 usages are pure JSON outer payloads such as donate/repost/legacy BTC like, while follow remains plain text and metafile entries use binary/index content types.\n\nVerification: node src/utils/metaidPinContent.test.mjs passed; git diff --check passed; pnpm exec tsc --noEmit still fails because of existing unrelated repo type errors (BuzzCard missing imports, package type path issues, mock Buzz shape gaps, etc.).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}