Since DT doesn’t store smart rules in a particular database and you can’t create one that is part of the global Inbox, at least that part of the behavio(u)r seems to be consistent.
I don’t think that’s universally true; as a test I just dropped a JPEG into the Inbox in the Finder - it was moved into the DT Global Inbox a few seconds later. When I dropped a file called ~$a bla test.docx into the Inbox in the Finder, that file remained put, and was not moved to the DT Global Inbox. That suggests to me the DT has some sort of selection routine (which presumably doesn’t include .dtSmartRule and .dtSmartGroup. There may be an advantage to this behaviour - I actually found the aforementioned file in the Inbox in Finder a while back - it had presumably been left there by Word, and it was never my intention for it to appear in the Global Inbox (or anywhere else). As such, I assume the selective behaviour is intentional.
At the same time, I can’t figure out what you are trying to achieve, so I can’t suggest a workaround.
Smart rules can be exported to the Finder, sent by email, and e.g., reimported to DEVONthink on another Mac. Drag a smart rule to the desktop to save it to a file or Control-click it and choose Export. Doubleclick a saved smart rule to import it, drag it into the sidebar, or Control-click into the sidebar and choose Import.
Edit: I mean that you could export the rules to Finder and then index that folder in DT.
Yes. That’s what I did before. But I saw Finder Inbox (that is the way to drop things into DT from Finder) and thought: exporting into Inbox should export into DT directly as copy.
What I should do is that: export to a folder in Finder (mostly Documents) and then drop into DT final backup folder.
Filesystem events used to monitor the inbox folder are only triggered by other applications but not by DEVONthink’s export, on startup the inbox folder is always checked and imported though.
I’ll have to check that during the week; the file I mentioned persisted in my Finder Inbox for days at a minimum though - and was never imported. I actively removed it and later dropped it back in, but it is possible some other factor than the name was responsible for the failure to import (as I said, the file shouldn’t have been there in the first place). I’ll see if I can investigate further, but this could be a red herring.