Align auto-translation trigger with bDS2 (manual save only, not publish) #87
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: Audit section 2.17. Related: #59 (saving a post triggers "create missing translations" task).
bDS2:
../bDS2/lib/bds/posts.exupdate_postschedules auto-translation only when called withauto_translate: true— an explicit manual editor save; comment: "never on post creation or autosave". Publish does not schedule translation.Current behaviour (RuDS):
crates/bds-ui/src/app.rscallsschedule_post_auto_translationfrom BOTHsave_post_editor(~line 5641) and the publish handler (~line 5947). The publish-time trigger is behaviour bDS2 does not have. Note #59 complains about the save-time trigger UX too — resolve both together.Spec:
specs/translation.alliumScheduleAutoTranslation fires onPostSavedForAutoTranslation(post)— save, not publish. Alsospecs/action_patterns.alliumAutoTranslationChain.Task: Clarify desired UX with the maintainer in light of #59, then: match bDS2 (drop the publish-time trigger) or update the spec if publish-time is wanted. Ensure autosave paths (if any) never schedule. All automatic AI activity must remain gated by airplane mode with local-model-or-toast per AGENTS.md — verify
schedule_post_auto_translation'sactive_endpointguard covers that.Acceptance: Trigger points match the decided spec; specs/translation.allium updated +
alliumvalidated; #59 cross-referenced.decision by the designer: auto-translation only happens on first manual save of a post. In that sense, follow bDS2 behaviour. also it might be that this is already covered in #59 so check what is still to be done for this topic.
Implemented in
2dcaf7f. Automatic post translation is now triggered only by an explicit manual canonical save; publishing no longer schedules missing translations, and autosave/internal persistence remains non-triggering. Added a red/green publish regression that confirms the post is published without AI tasks while the existing manual-save regression still uses the airplane endpoint and queues one task per missing language. Updated README plus specs/translation.allium and specs/action_patterns.allium, superseding #59's retained publish behavior. Targeted allium check/analyse report no diagnostics/findings; cargo build --workspace and cargo test --workspace pass. Neutral review matches bDS2's auto_translate-only update path.