Please address the comments from this code review:

## Overall Comments
- In `ControllerImpl::post_inactive` (NodeJS binding), the `EnvType` parameter is unnamed in the definition but `env` is used in the body, which will not compile—give the parameter a name (e.g. `maajs::EnvType env`) to match the usage.
- The `Tasker::run_task` logic that posts `controller_->post_inactive()` when `!task_runner_->pending()` may race with new tasks being queued immediately after the check; consider clarifying the intended semantics or tying the inactive transition more tightly to the runner state to avoid transiently marking the controller inactive while work is still being scheduled.

## Individual Comments

### Comment 1
<location path="source/binding/NodeJS/src/apis/controller.cpp" line_range="218-220" />
<code_context>
     return maajs::CallCtorHelper(ExtContext::get(env)->jobCtor, self, id);
 }

+maajs::ValueType ControllerImpl::post_inactive(maajs::ValueType self, maajs::EnvType)
+{
+    auto id = MaaControllerPostInactive(controller);
+    return maajs::CallCtorHelper(ExtContext::get(env)->jobCtor, self, id);
+}
</code_context>
<issue_to_address>
**issue (bug_risk):** The post_inactive implementation uses `env` but the parameter is unnamed, which will not compile.

This function declares `maajs::EnvType` without a name but then uses `env` in `ExtContext::get(env)`, which won’t compile. Please name the parameter and keep it consistent with the declaration, e.g.:

```cpp
maajs::ValueType ControllerImpl::post_inactive(maajs::ValueType self, maajs::EnvType env)
{
    auto id = MaaControllerPostInactive(controller);
    return maajs::CallCtorHelper(ExtContext::get(env)->jobCtor, self, id);
}
```
</issue_to_address>

Please address the comments from this code review:

## Overall Comments
- In `AsyncRunner::pending`, only checking whether the queue is empty may miss an in‑flight action; if the intent in `Tasker::run_task` is to post `inactive` only when there is no more work at all, consider also taking the current `running_` state into account (e.g. `pending() || running()`).
- In `ControllerImpl::post_inactive` (NodeJS binding), the implementation uses `ExtContext::get(env)` but the function signature does not name the `EnvType` parameter (currently `maajs::ValueType ControllerImpl::post_inactive(maajs::ValueType self, maajs::EnvType)`), which will not compile; update the signature to accept and use a named `env` parameter as done in other methods.

## Individual Comments

### Comment 1
<location path="source/binding/NodeJS/src/apis/controller.cpp" line_range="218-220" />
<code_context>
     return maajs::CallCtorHelper(ExtContext::get(env)->jobCtor, self, id);
 }

+maajs::ValueType ControllerImpl::post_inactive(maajs::ValueType self, maajs::EnvType)
+{
+    auto id = MaaControllerPostInactive(controller);
+    return maajs::CallCtorHelper(ExtContext::get(env)->jobCtor, self, id);
+}
</code_context>
<issue_to_address>
**issue (bug_risk):** The `post_inactive` implementation uses `env` but the parameter is unnamed, which will not compile.

In `ControllerImpl::post_inactive`, the second parameter is declared as an unnamed `maajs::EnvType`, but the body uses `env`, which is undefined and will cause a compile error. Name the parameter (e.g. `maajs::EnvType env`) so it matches the usage and the header declaration.
</issue_to_address>