Repository navigation
Conversation
lightcone-cli#241 lists outputs declared without a recipe in `lc status` as `no recipe`, and removes `ok` from the materialize report. - commands/materialize: drop `ok` from the JSON example; read the report by `up_to_date` (check) and `failed`/`blocked` (run); recipe-less outputs are never planned. - commands/status: the new state in the example, the states list and `counts`; the gate covers only outputs with a recipe. - concepts: `up_to_date` is the key to test; the check's scope. - agent-skills/lightcone: four states, and "done" also needs no `no recipe` output, matching agent-skills#54. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Documents the lightcone-cli behaviour from LightconeResearch/lightcone-cli#241, plus the matching skill change in LightconeResearch/agent-skills#54. Draft until a CLI release includes #241: the pages currently describe the released 0.5.0, which still has
okand doesn't list recipe-less outputs.What #241 changes
no recipestate. An output declared without a recipe used to vanish fromlc status. It's now listed with the stateno recipe, andcounts["no recipe"]counts such outputs.okkey. The materialize report no longer hasok. In check mode it saidtruewhile the command exited 1, and agents read it as "done".lc materialize --checkstill passes over recipe-less outputs, because it predicts what a run would do and a run skips them. "Finished" therefore means the check passes andlc statuslists nono recipeoutput.Pages
lightcone-cli/commands/materialize.mdx:okis gone from the JSON example; a check passes onup_to_date, a run succeeds whenfailedandblockedare empty; recipe-less outputs are never planned.lightcone-cli/commands/status.mdx: the new state in the example output (status column one character wider, as the CLI now prints it), in the states list, and incounts; a paragraph on the gate's scope.lightcone-cli/concepts.mdx:up_to_dateis the key to test; the check covers only outputs with a recipe.agent-skills/lightcone.mdx: four states, and the "done" and "ready to publish" conditions, matching agent-skills#54.Not changed:
lightcone-lab/features.mdxsays the Lab pipeline marks outputs "current, behind or stale". That depends on what the Lab renders, not on lc.npm run buildpasses.🤖 Generated with Claude Code