{"content":"Development diary for metaso-p2p commit 417ffd6 (fix: index host-prefixed published content paths).\n\nProduction investigation found why a recent simplebuzz pin was missing from the Bot Homepage v3 buzzes section. The source pin d712e4180adfdd9af527d714d8a1d8987d20435301d809793c176f1fb6e683c3i0 exists on MANAPI at MVC block 178466, and the production MVC parser also emits it. However, that parsed pin's path is host-prefixed as bc1p20k3x2c4mglfxr5wa5sgtgechwstpld80kru2cg4gmm4urvuaqqsvapxu0:/protocols/simplebuzz. The publishedcontent aggregator only matched pure protocol paths such as /protocols/simplebuzz, so it skipped the pin and never wrote the record or identity indexes.\n\nChange: publishedcontent protocol path normalization now strips a host-style prefix before /protocols/... while preserving the original SourcePath/CurrentPath in records. This makes host-prefixed simplebuzz, metaapp, and metabot-skill paths match the same protocol keys used by Bot Homepage sections.\n\nTest coverage: added TestProcessCreateAcceptsHostPrefixedProtocolPath, which reproduces the production shape and verifies the record is stored under /protocols/simplebuzz while retaining the original host-prefixed source path.\n\nVerification: CGO_ENABLED=0 go test ./internal/aggregator/publishedcontent -run TestProcessCreateAcceptsHostPrefixedProtocolPath -count=1 passed; CGO_ENABLED=0 go test ./internal/aggregator/publishedcontent ./internal/aggregator/bothomepage -count=1 passed.\n\nNote: this fixes new indexing for this path shape. Existing production gaps still need a replay/backfill over affected MVC heights or MANAPI data to populate already-missed simplebuzz records.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}