docs: improve project SEO metadata#246
Open
Drswith wants to merge 1 commit into
Open
Conversation
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
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
Improve Quantex search discoverability without expanding product scope:
Linked Artifacts
openspec/changes/improve-project-seoValidation
bun run memory:checkbun run lintbun run format:checkbun run typecheckbun run test(if behavior changed)bun run testwas not run because this change only updates package metadata, product README wording, and OpenSpec documentation. No CLI behavior, structured output, schema, install/update logic, or executable code changed.Additional validation:
bun run openspec:validatebun run openspec:status -- --change improve-project-seoRelease Intent
Docs Updated
docs/...openspec/...Scope Check
Closure Check
Notes
The OpenSpec change remains active by design until this implementation PR merges; archive closure should be handled by the normal agent-driven follow-up.