feat: paginate candidate model recommendations

This commit is contained in:
ar51
2026-09-01 09:48:01 +08:00
parent d97b788e0e
commit 8a695900f3
9 changed files with 598 additions and 52 deletions

View File

@@ -48,13 +48,26 @@ messages are ignored silently: the bridge sends no Feishu reply, makes no API
request, and appends no record. Only a message containing exactly one complete,
rule-valid eRob model and exactly one positive quantity enters the query workflow.
This gate applies even when the bot receives every message in a group; an @mention
alone does not bypass it. The bridge invokes only the existing controlled
delivery-prediction script. It generates the full Cartesian
alone does not bypass it. After a valid initial query, the same sender in the same
chat may ask whether there are other candidate models. The bridge keeps that
continuation context in memory for six hours, never shares it across senders or
chats, and stays silent if no matching context exists. A bridge restart clears
the context, so the sender must resend the complete model and quantity. The
continuation wording is flexible: `还有吗`, `有没有别的`, `再推荐几个`, `继续`,
`下一批`, and `more candidates` are examples rather than fixed commands. The
bridge still requires both continuation intent and valid context, so unrelated
phrases such as `more interesting` or `继续查询英语例句` do not trigger the old query.
The bridge invokes only the existing controlled delivery-prediction script. It
generates the full Cartesian
set of candidates allowed by the packaged Skill: brake upgrades, encoder
upgrades, sensor upgrades, low-temperature grease upgrades, and DZ/LF reducer
brand variants. Strong constraints and version stay unchanged. The original
model is queried first; valid candidates are reported in rule order, while
missing or unsupported candidates are summarized under `不可用候选`.
model is queried first as a baseline and does not count toward the recommendation
batch. The first reply queries at most four candidate models; a valid continuation
queries the next four without repeating earlier candidates or the original
baseline. Valid candidates are reported in rule order, while missing or
unsupported candidates are summarized under `不可用候选`.
On a managed network, the bridge uses the macOS system trust store. The proxy
root certificate must be installed and trusted under the AR51-approved network-access procedure; never disable TLS