Docs/runtime request: clarify legacy vs params response API and no-reply debugging path

[jini92]

MessengerBotR legacy / params API mismatch and no-reply debugging request

?????. MAIKAKAO(???? ??? conversational proxy) ??? ????? MessengerBotR ??? ???? ??? ?????, ??/??? ?? ??? ????.

??

???? ????? ?? ??? probe ??? ?? ????? ????.

??? ??? ??????.

• ??? ??? ?? ??
• ?? replier.reply(...) ?? ??
• ? ???? ? ??? ??? ??

??? ? ??? ??

1) response(...) API ??? ?/??? ?? ?????

???? ??? ?? ???? ?? ??? ??????.

function response(room, msg, sender, isGroupChat, replier, imageDB, packageName) {
  ...
}

??? ?? ??? ?/?? ??? ??? ??, ?? ????? ?? ??? ?? ??? ?????.

function response(params) {
  const room = params.room;
  const msg = params.msg;
  const sender = params.sender;
  const replier = params.replier;
}

?, ??? API? ????? / ??? ???? ??? ?? ?? ?? ??? ????, ?? ?? ??? ?? ?? ??? ??? ??? ???.

2) onCreate, onResume ?? lifecycle ??? ??? ??/??? ??? ??? ?????

?? ??? ? ?? ???? ????.

• There is no function onCreate
• There is no function onResume

??? ???? ? ?? placeholder? ??? ????.

function onCreate(savedInstanceState, activity) {}
function onResume(activity) {}
function onPause(activity) {}
function onStop(activity) {}

? ??? ??? ????, ????, ?? ???? ??? ? ???? ?????.

3) ?? probe ??? ???? ? ?? ??? ?????

???? ??? ?? ??? ?? ??? ???????.

function response(params) {
  if (!params || !params.replier) return;
  params.replier.reply("probe ok");
}

??? ? ???? ???? ???? ? ???, ???? ?? ??? ???? ?????.

• ?? ?? ?? ??
• ??? ?? ?? ??
• self-message / other-message ??
• ? ?? ?? ??
• API ???? ???
• ??? ?? ?? ??

????? ?? ?

A. ?? ??

???? ?? ???? ??? ??? ????? ?????.

1. ?? ?? response() ??
   • ?? response(room, msg, ...) ? ?? ???
   • ?? response(params) ? ?? ???
2. ??? API? ????? / ??? ???? ?? ??? ??
3. ?? ?? working probe ??
   • ??? ????? ?? ??? ??? ??
4. onCreate / onResume placeholder ?? ??

B. ???/UX ??

????? ??? ??? ???? ?? ?? ? ????.

1. ?? ?? ?? API mode ??
   • legacy / params mode
2. ????? ??? ???? ???? ??? ???? ??? runtime log
3. "?? ??"? ? ?? ?? ?????
   • notification access
   • room filter mismatch
   • self-message limitation
   • params/legacy mismatch

??

?? MessengerBotR? ?????,
?? ????? ?? ?? ??? ??? ????? "?? ?? ???"?? ??? ?????.

• legacy vs params callback mismatch
• lifecycle placeholder ambiguity
• notification/runtime capture uncertainty

? ??? ???? ?? ???? ???? ??? ?? ?? ? ????? ?? ??? ? ????.

?????.

[jini92]

Thanks — adding a few concrete follow-up questions from real-device Kakao group testing.

These are the exact points that would help us distinguish runtime behavior from script mistakes:

1. On 0.7.39a, what exact response(...) signatures are supported in practice?

   • response(room, msg, sender, isGroupChat, replier, imageDB, packageName)
   • response(params)
   • both, depending on settings?

2. If response(params) is supported, which exact app setting / script creation mode enables it?

   • Is it tied to "통합된 매개변수"?
   • Is it tied to "레거시 API를 사용합니다" being on/off?
   • Is it tied to the default script template generated by the app?

3. Are onCreate / onResume / onPause / onStop truly optional hooks?

   • We saw logs like There is no function onCreate and There is no function onResume.
   • Are these just benign logs, or can they affect runtime behavior in some configurations?

4. When a script compiles successfully but no reply is ever produced, what is the recommended minimum-debug path?
   For example, how should users distinguish between:

   • notification access problem
   • Kakao notification parsing problem
   • API signature mismatch
   • wrong script type (legacy vs api2)
   • room filter mismatch

5. Could the docs include one known-good minimal working probe for each mode?

   • one for legacy positional args
   • one for response(params) / unified params

The main confusion on our side was that it is currently possible to end up in a silent no-reply state with no obvious indication whether the problem is:

• runtime capture,
• API mode mismatch,
• or script template mismatch.

If there is a specific repo/docs location we should target for improving this, happy to follow up there too.