Repository navigation
feat(cli): drop the demo command - #526
Merged
Merged
Conversation
taskless onboard now writes rules for the project and reports what they found, which supersedes a fixed example rule. The demo assets stay: they are the source of the published reference.json conformance corpus, now read from disk by both the generator script and its test.
theCodeDrift
force-pushed
the
drop-demo-command
branch
from
October 16, 2026 23:36
c1af0d4 to
79bebaf
Compare
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.
Removes
taskless demo.taskless onboardnow writes rules for the project and reports what they found, which shows far more than a fixed example rule did.What changes
commands/demo.ts,rules/demo/rule.ts(the?rawembed of the example rules into the bundle), andtest/demo-command.test.ts.demofromindex.tsandSUBCOMMAND_NAMES, and drops it from the agent index's unlisted-command set along with the tests that guarded that.demoas live (demo-rule.yml,print-demo-manifests.ts,eslint.config.js, the dogfood scaffold test).What stays, deliberately
The
assets/demo-*rules are kept. They are the source of the published@taskless/cli/reference.jsonconformance corpus, so removing them would break that export, which is a separate decision from dropping the command.reference.test.tsused to check the corpus against the bundle's embedded copy. Now both it andscripts/write-reference.tsread the assets through one sharedreadReferenceInputs()inrules/demo/manifest.ts, so "the committed file is current" is a comparison against a fresh regeneration. TheDemo rulesworkflow still runs, as the only place the corpus rules' own fixtures execute.reference.jsonitself is byte-for-byte unchanged.Release note
None.
demowas never public API: it was unlisted from the agent index and undocumented, so there is nothing for a consumer to cross.Checks
pnpm typecheck,pnpm lint, and the CLI suite (128 files, 2361 tests) pass locally on the rebased branch.