From what we see :

• having phoenixd (LN nodeless) doesn't generate /.well-known/lnurlp/ln and doesn't give address when certifying nostr-bot
• nostr doesn't accept BOLT12 LN address for zap
• phoenixd doesn't allow to have non-BOLT12 static address

And, issues to review, for nostr-bots with a node :

• on amethyst (android nostr client), zaps are working for be-bop.io (mainnet)
• on amethyst (android nostr client), zaps are not working for dev-bootik2 (testnet) :
  
• on desktop web client (like primal.net or snort.social), no zap are working of live pilots with node :
  
  (but THERE IS a lightning address, seen onscreen)
  
  
  I know messages are coming from client, but it doesn't happen with a non-nostr-bot account
  Primat.net seems to need a web_ln_extension, as it triggers this on zap on real persons :
  

my bad, phoenixd provides a static, non-BOLT12 address : https://phoenix.acinq.co/server/api#get-lightning-address
we have to dig a bit