[codex] Add thread control rename ExecPlan#100
Draft
HatsuneMiku3939 wants to merge 1 commit into
Draft
Conversation
HatsuneMiku3939
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an active ExecPlan for renaming user-facing interactive thread controls from task vocabulary to thread vocabulary.
Background
The planned implementation should rename Discord actions, command option names, and one-shot routing syntax to
thread-*,thread_name,thread_id, andthread:<name>while keeping internal task persistence unchanged. Scheduled-task terminology remains unchanged because that product surface is genuinely task-oriented automation.Related issue(s)
None.
Implementation details
docs/exec-plans/active/20-rename-task-user-facing-thread-controls.md.docs/exec-plans/index.mdto list the new active plan.task:<name>prefixes, validation steps, and scheduled-task exclusions.Test coverage
make testmake lintNo separate e2e target exists in the repository Makefile.
Breaking changes
None. This PR only adds planning documentation.
Notes
Created by Codex