Create Workflow context that can be referenced in follow up workflows

Problem

User's would like to reference previous workflows when creating a new workflow. Currently there is no entity that can be easily referenced from within workflows since the context of a single workflow is mostly just the accumulation of its overall run

Desired Outcome

An entity exists that can serve as a structured input for follow up workflow runs if they want to reference what has happened beforehand.

Proposed solution

See

We could try to apply more structure onto the context entity in Duo Workflow, right now it is implicitly represented as messages inside conversation history. It might be helpful to make it more explicit, for example it could a structure as shown on (for ease of read) in the yaml below

context:
  repo_tree: |
    .
    ├── README.md
    ├── index.html
    ├── css
    │   └── style.css
    └── js
        └── script.js
  files: 
    - path: './js/script.js'
      content: "console.log("hello world")"
    - path: './index.html'
      content: "<!--add some content-->"
  project:
    id: 123
    url: https://gitlab.com/group/project
  workflow:
    id: 456
    plan: 
      - description: "Create basic structure for html page"
        status: "Completed"
      ....
    goal: "Scaffold set up for a static html page"
    summary: "We've created basic file structure for static html page"
  issues: ...
  mrs: ....
  ....

Also have a look at the discussions in Prevent "double work", e.g. reading files twice... (#285 - moved) around how we could better structure our context even for usage within a single run.