[Feature] API support or documentation for Auto coin rewards on tasks #290

Is your feature request related to a problem? Please describe.

I want tasks created through the API to use LifeUp's built-in Auto coin rewards, based on importance and difficulty. I don't want to calculate a number externally and save it as a Custom reward.

Is there already a supported way to do this with add_task or edit_task? I couldn't find it in the documentation.

Describe the solution you'd like

If this is already supported, please document the exact parameter and an example. If it isn't, please add an explicit way to select Auto or Custom independently for coins and XP, and expose the selected modes in task query results.

For example, a task created with importance 4 and difficulty 2 should be able to use the same Auto coin setting available in the phone's task editor. Editing its importance or difficulty should retain that mode.

Describe alternatives you've considered

Changing every imported task to Auto manually on the phone works, but adds maintenance to an otherwise automated workflow. Reimplementing the formula and writing numeric rewards would not preserve the native Auto setting.

Task templates looked promising because the release notes mention fixes for saving/restoring automatic coin reward status. However, the documented template API doesn't list an Auto coin parameter or a method to apply a template to create a task. Is there a supported template-based approach?

Additional context

Tested with LifeUp 1.107.3, LifeUp Cloud 3.0.3, API version 7, through the Cloud ContentProvider API.

Minimal request:

lifeup://api/add_task?todo=Temporary%20Auto%20test&importance=4&difficulty=2&skills=2&category=0

Observed behavior on disposable test tasks:

• Omitting coin and exp returned configured rewards of 0/0.
• Empty strings and the string auto did not trigger automatic calculation.
• coin=-1 was accepted literally as -1 coin, so it does not appear to be an Auto sentinel.
• Task query results don't expose Auto/Custom mode flags.
• Templates copied from tasks expose coinData and expData.isAutoSum, but these aren't documented API inputs. I understand that extra parameters may be ignored even when a request succeeds.
• Copying a task into a template may reconstruct numeric reward settings, so these tests do not establish the original task's UI mode.

All disposable test tasks and templates were removed; no test tasks were completed or rewards collected.

References:

• API documentation — task creation, editing, and templates
• FAQ — automatic reward calculation
• Release notes — automatic coin status in templates, v1.98.5 / v1.99.0