Skip to content

fix(config): one remedy for a UTF-16/UTF-32 .env; refuse the whole channel save - #17012

Merged
bolichen97 merged 2 commits into
kirodotdev:mainfrom
jeeshofone:fix/15596-wide-env-followup
Oct 8, 2026
Merged

bolichen97 merged 2 commits into
kirodotdev:mainfrom
jeeshofone:fix/15596-wide-env-followup

Conversation

@jeeshofone

@jeeshofone jeeshofone commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Follow-up to #15596.

Problem / Motivation

Goal: When the .env is saved as UTF-16 or UTF-32, every surface gives the one remedy that works (re-save it as UTF-8), and a refused channel save changes nothing, its sidebar folder included. That rollback is the same single step every channel save uses, so no saver can end with config.json and .env out of step.

On origin/main, a wide .env reads as unset, and two surfaces still act on that wrongly:

  • kirocrew service install warns that KIRO_API_KEY will not reach the service and tells the operator to printf ... >> <path>. Appending UTF-8 after a UTF-16/UTF-32 byte-order mark leaves a file the gateway still cannot read, so the service is still signed out after the restart. kirocrew doctor prints the gateway's "Save it as UTF-8" line and then that append remedy, which contradicts it.
  • The Discord and Telegram dashboard saves write config.json before the .env. That write drops the legacy bot_token the gateway is using while the .env is unreadable, then the .env write is refused with 409, so the bot loses its only token on the next restart. The 409 says "your other settings were saved", and the save skips its audit record.

Why it matters

Windows operators hit this with PowerShell's default >/Out-File. Following the install warning leaves them signed out with no further hint, and a Discord or Telegram save that looks harmless removes the working bot token.

Not a goal

  • Converting a wide .env to UTF-8 automatically.
  • Changing which keys the other channel saves (Slack, Teams, Webex, WeCom, Feishu) roll back when their .env write fails; they already undo their config on a 409. The changes on those saves are the two rows in the table below: Teams, Webex and WeCom now file the session folder after the .env write, and Slack keeps its config when cancelled after a landed write, as the other four already did.
  • The process environment after a save cancelled once its .env write landed: _write_env_or_roll_back re-raises the cancellation before the os.environ sync, so the old token stays in this process until restart. That is the behaviour on origin/main, and the .env and config.json on disk agree.

What changed (motivation → approach → change)

Surface Before After
service install / doctor kiro key block, wide .env append remedy (>>) the loader's decode sentence: file, "Save it as UTF-8", then add the key and restart
Discord / Telegram save, any failed .env write config.json kept (legacy bot_token dropped) config commit rolled back; the 409 reads "The .env was not changed." as on every other channel
Teams / Webex / WeCom save, refused .env write session folder created or renamed before the write folder filed only after the write lands, as every other channel save does
Slack save cancelled after its .env write landed config.json rolled back, so the new token sits beside the old settings config kept, as on Teams, Webex, WeCom and Feishu

undecodable_env_message in config/loader.py is the one sentence for an unreadable .env: the gateway logs it through warn_undecodable_env, and service/common.py prints it in headless_auth_warning when _names_defined_in_env_file raises EnvFileWideEncodingError. No second wide-encoding helper is added.

The Discord and Telegram saves already commit through _LockedSectionWrite, which can undo exactly the keys it wrote, legacy bot_token drop included. They now roll that commit back on any failed .env write, under the same live.hold() as the other savers. The session folder is created only after the .env write succeeds. _write_env_off_loop loses its config_kept option with the wording it selected.

The .env half of every channel save (the shielded write, the rollback on failure and the os.environ sync) is now one helper, _write_env_or_roll_back in handlers/messaging.py, which all seven savers call in place of their own copies. A cancellation drains the write and rolls back only when the write itself failed. The Slack copy lacked that guard and rolled back on any cancellation; it now behaves like the others. The config spec lists Discord and Telegram among the savers that hold the watcher across the pair.

Backwards compatibility

Compatible: only the failure paths change, and on those the old behaviour was a remedy that did not work and a partial save.

Reader: src/kiro_crew/dashboard/handlers/messaging.py:_write_env_off_loop (config_kept removed) -- entry: dashboard -- its only callers with the option were the Discord and Telegram saves, which now call _write_env_or_roll_back inside that rollback block; test_a_wide_env_refuses_the_save_and_leaves_the_config_as_it_was.
Reader: src/kiro_crew/service/common.py:_names_defined_in_env_file (raises for a wide file instead of returning an empty set) -- entry: CLI (service install, doctor) -- both callers, api_key_will_be_dropped and headless_auth_warning, handle the raise; test_service_warning_sees_a_bom_first_key, test_service_warning_still_fires_for_a_wide_file.

Tests

test/test_env_file_bom.py:

  • test_a_wide_file_is_told_to_re_save_not_to_append (UTF-16LE/BE, UTF-32LE/BE): the install warning carries the exact decode sentence and no >> or printf. Fails on origin/main.
  • test_doctor_prints_one_remedy_for_a_wide_file (same four): the doctor kiro key block says "Save it as UTF-8." and has no >>. Fails on origin/main.
  • test_a_wide_env_refuses_the_save_and_leaves_the_config_as_it_was (Discord, Telegram x four encodings): 409 ending "The .env was not changed.", .env byte-identical, the channel's config.json section (legacy bot_token included) unchanged, no audit record. Fails on origin/main.
  • test_any_failed_env_write_rolls_the_config_back (Discord, Telegram): an OSError from the .env write also leaves the section unchanged. With the rollback call removed from the Discord and Telegram failure branch, this and the previous test fail (10 cases).
  • test_the_session_folder_is_filed_only_after_the_env_write_lands (Teams, Webex, WeCom x refused, landed): a failed .env write files no folder, new or renamed; a landed one renames it. The three refused cases fail on the previous head.
  • test_service_warning_sees_a_bom_first_key now expects the raise for a wide file.

test/test_channel_env_write_off_loop.py:

  • test_every_saver_writes_env_through_the_shared_rollback_step (seven savers): each calls _write_env_or_roll_back once and never _write_env_off_loop or asyncio.shield itself. Fails on the previous head.
  • test_a_failed_write_rolls_back_and_raises, test_a_failed_write_with_no_config_commit_just_raises, test_a_cancelled_save_rolls_back_only_when_the_write_failed (landed, failed), test_a_landed_write_syncs_the_process_environment: the helper's contract. The environment-sync test scopes its probe variables with monkeypatch.context() and checks both are gone once that undo has run; the end-to-end saves put back every credential a landed save copies into os.environ; the cancellation test bounds the waits it releases itself.
  • test_the_config_and_env_writes_run_under_the_live_config_hold (Discord, Telegram): both writes run with the watcher held, and the hold is released after.

test/test_slack_config_handlers.py:

  • test_slack_cancellation_after_successful_env_write_does_not_rollback_config: a Slack save cancelled after its .env write committed keeps the new command in config.json beside the new token. Fails on the previous head's Slack saver, which rolled the config back.

Run: every test file that drives the channel saves or the shared writers (test_channel_env_write_off_loop, test_config_rmw_preserves_settings, test_config_savers_locked_write, test_discord_config_handlers, test_telegram_config_handlers, test_slack/feishu/wecom_config_handlers, test_handlers_messaging_composition_contract, test_no_config_dir_in_async) plus test_service.py and test_env_file_bom.py: 813 passed, 4 skipped on base 782dedd. On the current head (base b13cebd): every channel's config-handler tests, test_channel_env_write_off_loop, test_config_savers_locked_write, test_handlers_messaging_composition_contract, test_env_file_bom, test_config_live, test_service and test_config_load_pipeline, plus test_source_pin_budget: 1120 passed, 3 skipped. After the folder-order change: every test file that names session_folder or ensure_channel_folder (17 files) 1358 passed, 1 skipped, and the channel save files above 1818 passed. After the rebase onto 3343351 (unchanged range-diff): the channel save files, test_channel_env_write_off_loop, test_config_savers_locked_write, test_handlers_messaging_composition_contract, test_env_file_bom, test_service, test_source_pin_budget and test_kas_login_loopback: 975 passed, 4 skipped. scripts/local-gate.py related set on the first head: 46431 passed; its 29 failures (test_design_tweak_*, two test_cli.py doctor STT tests, test_config_validation, test_auto_improvement_members, test_home_pin_survives_monkeypatch_undo) fail identically on bare origin/main af1eb61 on the same host. black gate, isort, flake8, mypy on the changed files and the comment-history gate pass.

Manual verification

N/A -- unit coverage sufficient: the tests drive the real headless_auth_warning, the doctor kiro key check and the real Discord/Telegram handlers against wide files and a failing .env write.

Related Issues

Closes #17000

Pattern harvest

Rule candidate: review-prompt
Pattern: a save that commits one store before validating the input another store's write needs, so a later refusal leaves a partial save.

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@jeeshofone
jeeshofone requested a review from a team as a code owner October 5, 2026 11:14
@jeeshofone
jeeshofone requested a review from bolichen97 October 5, 2026 11:14
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 5, 2026
@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5, fork) — ✅ PASS

Design-level review of a6351203242e8e43f3f0069871ad2e11d1ad4cc9 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Nothing to check.

[DESIGN-REVIEWED] a635120

Description read

[DESCRIPTION-READ] 67e103351b7d6313c1a821c9b5a631012f26430691daa6260eec04b826d9d04f

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5, fork) — ✅ PASS

Premise-level review of a6351203242e8e43f3f0069871ad2e11d1ad4cc9 via the fork AI-review pipeline — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Check that the maintainers agree to reverse #15596's "config kept" choice for Discord and Telegram. The PR's reason: that write drops the legacy bot_token the gateway falls back to.

What this change ships

Inventory (9 items) — 9 justified

Intent: a Windows operator with a UTF-16/UTF-32 .env gets the one remedy that works, and a refused channel save leaves nothing changed. This is a FIX.

  1. service install and doctor tell you to re-save a wide .env as UTF-8 instead of appending to it — justified
  2. A Discord or Telegram save whose .env write fails now rolls back config.json, so the legacy bot_token survives — justified
  3. Discord and Telegram saves now hold the live-config watcher across the config and .env writes — justified
  4. The 409 drops "your other settings were saved" and now reads "The .env was not changed." — justified
  5. Teams, Webex and WeCom create or rename the sidebar folder only after the .env write lands — justified
  6. Seven copies of the write / roll back / environment-sync code become one _write_env_or_roll_back — justified
  7. A Slack save cancelled after its .env write landed keeps its config, as the other savers already did — justified
  8. undecodable_env_message is the single decode sentence, with 2 consumers (warn_undecodable_env, headless_auth_warning) — justified
  9. _names_defined_in_env_file raises for a wide file, and both its callers handle the raise — justified

[FIRST-PRINCIPLES-REVIEWED] a635120

Description read

[DESCRIPTION-READ] 8647fe1a1adb3a11816c5ca2868045d9eee91dd056741bb6f4c4f25e7fdb525e

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review (fork) — ✅ no blocking findings

Reviewed a6351203242e8e43f3f0069871ad2e11d1ad4cc9 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] a635120

@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review (fork) — ✅ no blocking findings

Reviewed a6351203242e8e43f3f0069871ad2e11d1ad4cc9 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] a635120

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 5, 2026
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch from 0bb6f98 to 7f4f1f3 Compare October 5, 2026 13:05
@jeeshofone

Copy link
Copy Markdown
Contributor Author
  • The pre-check fixes one failure class, not the write order.

fixed in 7f4f1f3: the encoding pre-check is removed. Discord and Telegram now write the .env through _write_env_or_roll_back, which calls the existing _LockedSectionWrite.rollback on any failed .env write (OSError, a wide file, a non-wide decode error), as Slack, Teams, Webex, WeCom and Feishu already do, under the same live.hold().
test_any_failed_env_write_rolls_the_config_back pins the OSError case; the wide case is test_a_wide_env_refuses_the_save_and_leaves_the_config_as_it_was. Removing the rollback call fails both (10 cases).

@jeeshofone

Copy link
Copy Markdown
Contributor Author
  • Item 3 -- symptom-level pre-check

fixed in 7f4f1f3: the pre-check is replaced by the existing rollback, as this item asks. _write_env_or_roll_back undoes the Discord/Telegram config commit (legacy bot_token drop included) on any failed .env write, so the 409 and every other failure leave config.json as it was.
No new failure mode is handled separately: the wide-encoding refusal stays in _write_env_off_loop, shared by all channels.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 5, 2026
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch from 7f4f1f3 to 4031fae Compare October 5, 2026 18:25
@jeeshofone

Copy link
Copy Markdown
Contributor Author

New head 4031fae: the same single commit rebased onto main c6bfd72 (range-diff identical to 7f4f1f3, no content change). Every review lane on 7f4f1f3 was PASS or no findings, so no review span is open.

The two reds on 7f4f1f3 were outside this diff:

  • Backend Tests (Windows) (6): test/test_subagent_queue_max_wait.py::TestAnEndedParent::test_an_ended_parents_row_is_stopped_not_expired TimeoutError (1 failed, 20803 passed; job 111779669376). The same file fails on Windows (6) on an unrelated PR with a different test, and this PR does not touch subagent queueing.
  • Backend Lint & Type Check (3.12): cancelled during the Type check (mypy) step at about 25 min (job 111779668864). Lint jobs across the repo ran 18 to 26 min today and other PRs' Lint jobs were cancelled the same way. mypy on the five changed source files passes locally.

Rerun on the new head: the 12 channel-save, writer and service test files listed in the description (813 passed, 4 skipped), plus test_config_loader.py; isort, flake8 and mypy on the changed files; the comment-history gate.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 5, 2026
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 5, 2026
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch from 4031fae to eb1c4d8 Compare October 5, 2026 22:14
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 5, 2026
@github-actions github-actions Bot added the readiness: action required A blocking check or review needs attention label Oct 6, 2026
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch 2 times, most recently from f295a5f to 3f790b2 Compare October 6, 2026 07:55
@jeeshofone

Copy link
Copy Markdown
Contributor Author
  • Autouse teardown undoes other fixtures' shared patches (test/test_channel_env_write_off_loop.py:120, reviewed f295a5f)

    fixed in 3f790b2: the autouse fixture and its monkeypatch.undo() are gone. The environment-sync test now sets its two probe variables inside with monkeypatch.context() as env: and, after that block's own undo has run, asserts that neither KC_PROBE_SET nor KC_PROBE_CLEARED is in os.environ. No shared fixture's patches are touched. Checked by mutation: dropping the seeding setenv and making the delenv non-raising (the shape that leaked) fails that test on the post-block assertion. The end-to-end saves keep their explicit try/finally that puts back every key a landed save copied into os.environ.

  • Cancellation regression waits lack local deadlines (test/test_channel_env_write_off_loop.py:301, reviewed f295a5f)

    fixed in 3f790b2: the parked writer's release.wait() and the test's await save both run under asyncio.wait_for(..., timeout=_LOST_RUN_CEILING_SECS), a named 10 s ceiling, which is the bound this module's other self-released waits (finish.wait(timeout=10), wait_for(second, timeout=10)) already use. A stalled drain now fails at that line with TimeoutError instead of reaching the worker timeout.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026
@jeeshofone

Copy link
Copy Markdown
Contributor Author
  • Item 6 -- a Slack save cancelled after its .env write landed now keeps its config (rides along) (reviewed 3f790b2)

    Kept, and it is not separable from item 7. The Design review on 3eb7fe5 flagged the shielded .env write and rollback as a sixth hand-copied block, and item 7 answers that with one step every saver calls. Slack's copy was the only one that rolled the config back on a cancellation after the write had landed. Keeping that behaviour would need a Slack-only branch in the shared step, which is the per-saver copy item 7 removes.
    The old Slack behaviour was also wrong on its own terms: test_slack_config_handlers.py::test_slack_cancellation_after_successful_env_write_does_not_rollback_config cancels a Slack save after the .env write committed and fails on the previous Slack saver, which left the new token in .env beside the old config.json. Teams, Webex, WeCom and Feishu already kept the config in that case. The description's change table, the What changed paragraph and the Not a goal line all name this one Slack change, so a reviewer sees it before merge.

@jeeshofone

Copy link
Copy Markdown
Contributor Author

Head 3f790b2 (base e1999e4): every review lane passes, and both GPT findings on f295a5f are answered above. The test reds on this head are outside this diff:

test_decisions_compaction_keep.py::TestRun::test_a_run_that_outlives_its_budget_records_the_timeout, red on Windows (5) at c312bc0 (assert [] == ['run-timeout'], outside this diff, no tracking issue), passed on both later heads.

@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch 2 times, most recently from edb3487 to f138589 Compare October 6, 2026 11:27
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch from f138589 to 2126371 Compare October 6, 2026 11:57
@jeeshofone

Copy link
Copy Markdown
Contributor Author
  • Check before merge -- Discord/Telegram now roll back on a 409, reversing fix(config): read a byte-order-marked .env the same way everywhere #15596's "your other settings were saved" (reviewed 2126371)

    Confirmed: fix(config): read a byte-order-marked .env the same way everywhere #15596 came from this same author, and this follow-up reverses that choice on purpose. On a wide .env the "other settings" that were kept included the config write that drops the legacy bot_token, which is the only token the gateway can read while the .env reads as unset. So the kept half removed the working credential, and the 409 told the operator nothing was lost. test_a_wide_env_refuses_the_save_and_leaves_the_config_as_it_was (Discord, Telegram x four encodings, fails on origin/main) and test_any_failed_env_write_rolls_the_config_back pin the new behaviour. The description's Problem section and change table name the reversal.

Head 2126371 also moves the Teams, Webex and WeCom folder step after the .env write (item 5), with test_the_session_folder_is_filed_only_after_the_env_write_lands; its three refused cases fail on the previous head.

… failed channel save

A wide .env reads as unset, so service install warned with its append remedy,
which leaves the file unreadable after the restart it asks for. The warning now
prints the loader's shared decode sentence (file plus "Save it as UTF-8") for a
wide file and drops the append, and doctor's kiro key block agrees with the
gateway's decode line.

The Discord and Telegram saves wrote config.json, dropping the legacy bot_token
the gateway falls back to while the .env is unreadable, and kept it when the
.env write then failed. They now undo the config commit on any failed .env
write with the same shielded rollback block the other channel saves use, under
the same live-config hold.
A refused save changes nothing on every channel, so the config_kept wording is
gone.

Closes kirodotdev#17000
…back step

Each of the seven channel savers carried its own copy of the shielded .env
write, the config rollback and the os.environ sync. The Slack copy had the
rollback but not the cancellation guard, so a cancel that arrived after its
.env write landed rolled config.json back and split the pair.

_write_env_or_roll_back in handlers/messaging.py now holds that step once and
every saver calls it. A test pins that no saver writes .env any other way, and
the helper's own tests cover a failed write, a cancel after a landed write, a
cancel after a failed write and the environment sync. The config spec now lists
Discord and Telegram among the savers that roll back under live.hold(), with a
hold test for both.

The environment-sync test scopes its probe variables with
monkeypatch.context() and checks both are gone once that undo has run, the
end-to-end saves put back every credential a landed save copies into
os.environ, and the cancellation test bounds the waits it releases itself.
@jeeshofone
jeeshofone force-pushed the fix/15596-wide-env-followup branch from 2126371 to a635120 Compare October 6, 2026 15:46
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Reviewed, not approving (crew-pr-reviewer). The direction is good: one remedy sentence everywhere, and every channel save now rolls its config.json half back when the .env write fails, so Discord and Telegram no longer drop the bot token. But this changes how credentials are written for all seven channel savers, how os.environ is updated with token values, and the service install / doctor credential guidance. Our review rules leave credential-handling changes to a security owner.

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sensitive change review

Head commit: a635120

  • Rule changed: channel .env write failure handling
  • Before -> after: config.json write stayed committed when .env write failed -> config is rolled back on a failed .env write
  • Worst case if wrong: a failed save leaves previous config (user retries); no secret exposure
  • Evidence checked: full diff read; tests on the PR read; Security Scope Review and PR Readiness green on this head; no owner/operator gate added or removed.
  • No regression: normal-user workflows unchanged; only the stated path differs.
  • How to undo: revert the squash commit.

@bolichen97
bolichen97 merged commit bb40f79 into kirodotdev:main Oct 8, 2026
104 checks passed
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UTF-16/UTF-32 .env: service install says to append, and Discord/Telegram saves drop the legacy token on a 409

3 participants