Yeah, I basically landed on the same workaround to remove farm: part of dependency declaration. Alongside asset, I was also declaring dependency on farm_log and since it already depends on asset I just removed explicit dependency on asset and currently using just farm_log without farm: part as a dependency.
It may be worth adding a note about this workaround and need for it on farmOS module development | farmOS for future reference.
I decided to add a category as it doesn’t require adding new filter type to filter termination logs and provides more compatibility with the workflow @gbathree already is using for asset termination.
Is termination field is treated as the source of truth, but the category is also added always when saving log changes and the log is completed and marked as termination, so it should be pretty consistently set when the log is treated as termination.
Ah, yes it already works that way, earlier when talking about referenced assets I meant assets added in the asset field.