Ting/workflows
Watch
2
0
Fork
You've already forked workflows
 0
Code Issues 28 Pull requests Projects Releases Packages Wiki Activity Actions

feat(engine): thinned wf command surface in embedded Nushell #7

New issue
Closed
opened 2026-09-09 10:08:48 +00:00 by larandar · 1 comment
larandar commented 2026-09-09 10:08:48 +00:00
Owner
Copy link

Proposal

Expose only the intentionally supported wf command surface inside embedded Nushell.

Design

Implement native wf workspace operations (init, diff, checkpoint), wf branch, wf gate, and wf artifact; do not expose unthinned command families.

Tasks

  • 3.1 Implement wf workspace init, diff, and checkpoint.
  • 3.2 Implement wf branch.
  • 3.3 Implement wf gate.
  • 3.4 Implement wf artifact.
  • 3.5 Verify that no unthinned commands exist.

Gherkin Specification Delta

must.contracts.ting-workflows.executor.wf-command-surface

Scenario: Use the thinned wf command surface

  • GIVEN an embedded workflow session
  • WHEN a caller invokes the supported wf commands
  • THEN workspace init, diff, checkpoint, branch, gate, and artifact operations are available
  • AND an unthinned or unsupported command is rejected as unavailable.
## Proposal Expose only the intentionally supported `wf` command surface inside embedded Nushell. ## Design Implement native `wf workspace` operations (init, diff, checkpoint), `wf branch`, `wf gate`, and `wf artifact`; do not expose unthinned command families. ## Tasks - 3.1 Implement `wf workspace init`, `diff`, and `checkpoint`. - 3.2 Implement `wf branch`. - 3.3 Implement `wf gate`. - 3.4 Implement `wf artifact`. - 3.5 Verify that no unthinned commands exist. ## Gherkin Specification Delta ### must.contracts.ting-workflows.executor.wf-command-surface **Scenario: Use the thinned wf command surface** - **GIVEN** an embedded workflow session - **WHEN** a caller invokes the supported `wf` commands - **THEN** workspace init, diff, checkpoint, branch, gate, and artifact operations are available - **AND** an unthinned or unsupported command is rejected as unavailable.
larandar commented 2026-09-09 10:15:29 +00:00
Author
Owner
Copy link

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fastlane
tango/2-ting-workflow-executor
No results found.
Labels
Clear labels
  
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Meta/Campaign
Campaign grouping node; dependencies name its direct Epics

  
Meta/Epic
Epic grouping node; dependencies name its direct Sessions

  
Meta/Session
Session delivery bundle; dependencies name its direct leaf issues

  
Priority/Critical
The priority is critical

  
Priority/High
The priority is high

  
Priority/Low
The priority is low

  
Priority/Medium
The priority is medium

  
Reviewed/Confirmed
Issue has been confirmed

  
Reviewed/Curated
PR LABEL: merge by rebase/ff to preserve the commit line; absence means squash. Set by the AUTHOR. (Curation itself is a duty on every PR — the label only picks the merge style.)

  
Reviewed/Duplicate
This issue or pull request already exists

  
Reviewed/Invalid
Invalid issue

  
Reviewed/Won't Fix
This issue won't be fixed

  
Scope/Campaign
Umbrella issue grouping a coherent multi-issue campaign.

  
Status/Abandoned
Somebody has started to work on this but abandoned work

  
Status/Blocked
Something is blocking this issue or pull request

  
Status/Conflicted
STATE: steward rebase failed; work returned to its agent, with evidence.

  
Status/In Progress
STATE: claimed, workspace active. Exactly one assignee, or none when idle.

  
Status/In Review
STATE: PR open against fastlane. Set by steward (PR webhook).

  
Status/Need Grooming
Issue body and comments do not yet conform to the Deliverable record; grooming required.

  
Status/Need More Info
Feedback is required to reproduce issue or to continue work

  
Status/Ready
Ready for execution; no known blocker prevents useful work from starting.

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#8 feat(workflows): dynamic sub-workflow command registration, tool projection & mutual exclusion
Ting/workflows
Depends on
#4 feat(engine): embedded Nushell engine with in-process stream combinators
Ting/workflows
Reference
Ting/workflows#7
No description provided.