Persist artifact language for OpenFlow init#15
Open
lininn wants to merge 5 commits into
Open
Conversation
OpenFlow init now records a project-level artifact language preference in openspec/config.yaml so generated proposals, plans, workflow status, and user-facing summaries can follow the project's documentation language without re-detecting it in each phase. The spec and amend handoff templates propagate that preference into plan-ready generation while keeping OpenSpec schema markers, CLI commands, code identifiers, and protocol keywords in their required original form. This also bumps the package to the published beta version. Constraint: User requested a beta release and PR from the current release branch. Rejected: Store language preference in a separate runtime state file | openspec/config.yaml is already the project-level context source consumed by later phases. Confidence: high Scope-risk: narrow Directive: Do not translate parser-required OpenSpec headings when language.artifacts is non-English. Tested: npm run check Tested: openspec validate add-openflow-init-phase --strict Tested: npm publish --tag beta published @lininn/openflow@0.4.5-beta.0 Co-authored-by: OmX <omx@oh-my-codex.dev>
- Add Grill decision gate: capture phase is blocked until user decides - Change nextCommand from /openflow spec to /openflow grill when proposal exists - Add project init guard to brainstorming template (matching proposal) - Tighten init skip: require explicit user intent, not passive silence - Rename '项目初始化守卫' to 'OpenSpec 初始化入口门禁' - Restrict init guard to proposal/brainstorming entry phases only
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
language.artifactsscaffold toopenspec/config.yamlduring OpenFlow init.0.4.5-beta.0.Beta Publish
@lininn/openflow@0.4.5-beta.0with npm dist-tagbeta.latestremains0.4.4andbetapoints to0.4.5-beta.0.Test Plan
npm run checkopenspec validate add-openflow-init-phase --strictnpm publish --tag beta --dry-run