chore: reject invalid tasks on client

[frrist]

closes #969

Ideally, this check would be performed once in a job run Before option, but that would break the survey command since it uses different task names. This is making me rethink if the survey job should go somewhere else. Thoughts?

[kasteph]

🚀

[placer14]

What was the motivation for separating peeragents again? IIRC, it was primarily a behavorial difference in that it was indexing external/ephemeral data and not local data. Which means it probably doesn't need the majority of the machinery that all of the other commands use. So maybe there is a separate binary here which just consumes a node API? ...lotus-survey effectively becomes just lotus with some API<->DB interactions on top.

[placer14]

Why twice? No objection but it's unusual.

[frrist]

Its different. TaskLookup vs TableLookup where TableLookup contains the granular task names.

[frrist]

What was the motivation for separating peeragents again? IIRC, it was primarily a behavorial difference in that it was indexing external/ephemeral data and not local data

Yeah, the Surveyer collects information on peers lily is connected to, meaning it doesn't inspect the chain - unlike the rest of the tasks.

Which means it probably doesn't need the majority of the machinery that all of the other commands use. So maybe there is a separate binary here which just consumes a node API? ...lotus-survey effectively becomes just lotus with some API<->DB interactions on top.

Yeah, it needs a DB and an API. It may be the case that drone already does some of this, do you know?