Exercise draft of Copilot modernize my legacy code (#1)

* Refactor exercise structure and update workflows for modernizing legacy COBOL application

- Removed outdated step files and replaced with new structured steps for the exercise.
- Added new step files for creating a test plan and converting COBOL code to Node.js.
- Updated workflows to reflect new step files and ensure proper execution order.
- Enhanced README with clear objectives and prerequisites for the exercise.
- Introduced COBOL source files for the legacy accounting system.
- Updated .gitignore to exclude COBOL binaries and Node.js modules.

* Update README.md

fix default template naming

Author: arilivigni

.devcontainer/devcontainer.json

@@ -0,0 +1,30 @@
+{
+  "name": "copilot-flow-state",
+  "image": "mcr.microsoft.com/devcontainers/base:jammy",
+  "features": {
+    "ghcr.io/devcontainers/features/docker-in-docker:2": {},
+    "ghcr.io/devcontainers/features/github-cli:1": {},
+    "ghcr.io/devcontainers/features/node:1": {
+      "version": "lts",
+      "pnpmVersion": "latest",
+      "nvmVersion": "latest"
+    }
+  },
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "GitHub.copilot-insiders",
+        "dbaeumer.vscode-eslint",
+        "DavidAnson.vscode-markdownlint",
+        "bierner.markdown-mermaid",
+        "bitlang.cobol"
+      ],
+      "settings": {
+        "chat.agent.enabled": true,
+        "chat.mcp.enabled": true
+      }
+    }
+  },
+  "forwardPorts": [],
+  "postCreateCommand": "sudo chmod +x ./.devcontainer/*.sh && sudo ./.devcontainer/postCreate.sh"
+}

.devcontainer/postCreate.sh

@@ -0,0 +1,5 @@
+#!/bin/bash
+
+# Update packages and install GnuCOBOL
+echo "Installing GnuCOBOL compiler..."
+sudo apt-get update && sudo apt-get install -y gnucobol

.github/copilot-instructions.md

@@ -0,0 +1,28 @@
+## Custom Instructions for Copilot: COBOL Dev Container Setup
+
+When working in this repository, follow these steps to automate the COBOL application setup after the dev container is created:
+
+1. Navigate to the COBOL source directory:
+
+   ```bash
+   cd /workspaces/copilot-modernize-your-legacy-code/src/cobol/
+   ```
+
+1. Compile the COBOL application:
+
+   ```bash
+   cobc -x main.cob operations.cob data.cob -o /workspaces/copilot-modernize-your-legacy-code/accountsystem
+   ```
+
+1. Return to the project root:
+
+   ```bash
+   cd /workspaces/copilot-modernize-your-legacy-code/
+   ```
+
+1. The compiled application can be run with:
+   ```bash
+   ./accountsystem
+   ```
+
+These steps ensure the COBOL application is built and ready to use in the dev container environment.

.github/steps/1-preparing.md

@@ -0,0 +1,96 @@
+## Step 1: Help me modernize Copilot
+
+Welcome to Merginton High School's IT team! You've joined at a critical time. The school has been using the same COBOL-based accounting system since the early 1990s to manage student fees, cafeteria accounts, and school supplies purchases. The original programmer retired years ago, and the current IT staff struggles to maintain the system whenever changes are needed.
+
+### 📖 Theory: Educational Legacy Systems Modernization
+
+> [!NOTE]
+> Legacy code modernization in educational settings means transforming outdated systems into modern technologies while preserving essential school business operations and data integrity.
+
+Many educational institutions still rely on legacy COBOL systems for critical administrative functions. While these systems have reliably managed school finances for decades, they now present significant challenges:
+
+- Few IT staff with COBOL knowledge remain in the education sector
+- Limited integration with modern school management systems and online payment platforms
+- Difficulty supporting new educational programs and fee structures
+- Rising maintenance costs eating into limited school technology budgets
+
+Modernizing the school's accounting system will provide numerous benefits:
+
+- Seamless integration with student information systems and online payment portals
+- Better reporting capabilities for administrative decision-making
+- Easier maintenance by the existing IT team
+- Ability to quickly adapt to new educational programs and fee structures
+
+GitHub Copilot can transform this modernization process by:
+
+1. Helping decipher the decades-old COBOL code that lacks documentation
+1. Translating COBOL structures to modern Node.js equivalents
+1. Suggesting modern approaches to student account management
+1. Assisting with test creation to ensure student financial data remains accurate
+
+### ⌨️ Activity: Setting Up Your Environment
+
+To get started, we will set up a GitHub Codespace with the necessary tools and extensions to use GitHub Copilot effectively.
+
+> [!TIP]
+> You can learn more about current and upcoming features in the [GitHub Copilot Features](https://docs.github.com/en/copilot/about-github-copilot/github-copilot-features) documentation.
+
+1. Left-click the below button to open the **Create Codespace** page in a new tab. Use the default configuration.
+
+   [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/{{full_repo_name}}?quickstart=1)
+
+1. Confirm the **Repository** field is your copy of the exercise, not the original, then click the green **Create Codespace** button.
+
+   - ✅ Your copy: `/{{{full_repo_name}}}`
+   - ❌ Original: `/skills/getting-started-with-github-copilot`
+
+1. Wait a moment for Visual Studio Code to load in your browser.
+
+1. In the left sidebar, click the extensions tab and verify that the `GitHub Copilot` and `Python` extensions are installed and enabled.
+
+   <img width="350" alt="copilot extension for VS Code" src="https://github.com/user-attachments/assets/ef1ef984-17fc-4b20-a9a6-65a866def468" />
+
+1. At the top of VS Code, locate and click the **Copilot icon** to open a Copilot Chat panel.
+
+   <img width="150" alt="image" src="https://github.com/user-attachments/assets/5e64db46-95cb-415d-badc-b6b8677f10c1" />
+
+1. If this is your first time using GitHub Copilot, you will need to accept the usage terms to continue.
+
+### :keyboard: Activity: Use Copilot to help remember a terminal command 🙋
+
+Great work! Now that we are familiar with the app and we know it works, let's ask copilot for help starting a branch so we can do some customizing.
+
+1. If not already there, return to VS Code.
+
+1. In the bottom panel, select the **Terminal** tab. On the right side, click the plus `+` sign to create a new terminal window.
+
+   > **Note:** This will avoid stopping the existing debug session that is hosting our web application service.
+
+1. Within the new terminal window use the keyboard shortcut `Ctrl + I` (windows) or `Cmd + I` (mac) to bring up **Copilot's Terminal Inline Chat**.
+
+1. Let's ask Copilot to help us remember a command we have forgotten: creating a branch and publishing it.
+
+   > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
+   >
+   > ```prompt
+   > Hey copilot, how can I create and publish a new git branch called modernize-legacy-code?
+   > ```
+
+   > **Tip:** This is a simple example, but Copilot is great at providing more tailored commands that might involve loops, pattern matching, file modification, and more! Don't be afraid to ask Copilot for a suggestion. Just remember it is a suggestion and you should always verify it first to be safe.
+
+   ```shell
+   git checkout -b modernize-legacy-code
+   git push -u origin modernize-legacy-code
+   ```
+
+1. Now that we are happy with the command, press the `Run` button to let Copilot run it for us. No need to copy and paste!
+
+1. Now that your branch is pushed to GitHub, Mona should already be busy checking your work. Give her a moment and keep watch in the comments. You will see her respond with progress info and the next lesson.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+- If you don't see the Copilot icon, make sure you have the GitHub Copilot extension installed and enabled.
+- If you don't see the Copilot chat panel, try reloading the codespace or checking your extension settings.
+- If Copilot doesn't understand your command, try rephrasing it or providing more context.
+- If you encounter any issues with the terminal, make sure you have the correct permissions to create branches in the repository.
+</details>

.github/steps/1-step.md

@@ -0,0 +1,70 @@
+## Step 2: Understanding the School's Legacy COBOL Accounting System
+
+In this step, you'll explore the school's legacy COBOL accounting system to understand its structure and functionality. This will help you prepare for the modernization process.
+
+### ⌨️ Activity: Exploring the School's Legacy Accounting System
+
+1. Take a few minutes to explore the COBOL files in the repository (`main.cob`, `operations.cob`, and `data.cob`)
+1. Open `src/cobol/main.cob`, `src/cobol/operations.cob`, `src/cobol/data.cob` and select "Agent" from the Copilot Chat window.
+1. click "Add Context..." in the Copilot Chat sidebar and click "Open Editors" to add the open COBOL files as context.
+1. Explain the purpose of each file in the context of the school's accounting system:
+   - `main.cob`: This file contains the main program logic for managing student accounts, including user interaction and menu options.
+   - `operations.cob`: This file implements the core operations for processing payments, recording purchases, and managing student balances.
+   - `data.cob`: This file handles data storage and retrieval for student account balances.
+1. Create a docs/README.md file in the repository and document your findings, including:
+   - The purpose of each COBOL file
+   - Key functions and operations performed by the system
+   - Any specific business rules or constraints related to student accounts
+  
+    > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
+    >
+    > ```prompt
+    > @workspace Create a README.md file in a new /docs directory folder in the repository. Document the purpose of each COBOL file, key functions, and any specific business rules related to student accounts.
+    > ```
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- COBOL is a column-sensitive language. The code is organized in divisions (IDENTIFICATION, DATA, PROCEDURE) and sections.
+- The `main.cob` file handles the user interface and menu options (view student balance, process payment, record purchase, exit)
+- The `operations.cob` file contains the logic for different student account operations
+- The `data.cob` file manages the storage of student account balances
+
+</details>
+
+### ⌨️ Activity: Create a data flow diagram
+
+Create a Mermaid data flow diagram (DFD) that illustrates how data moves through the school's accounting system.
+
+  > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
+  >
+  > ```prompt
+  > @workspace can you create a sequence diagram of the app showing the data flow of the app. Please create this in mermaid format so that I can render this in the docs/README.md markdown file.
+  > ```
+
+Make sure you can preview the diagram in the `docs/README.md` file.
+
+1. In the left sidebar, select the `Source Control` tab and make sure you are making changes on `modernize-legacy-code`branch.
+
+   > **Tip:** Opening a file from the source control area will show the differences to the original rather than simply opening it.
+
+1. Find the `docs/README.md` file and press the `+` sign to collect your changes together in the staging area.
+
+1. Above the list of staged changes, find the **Message** text box, but **don't enter anything** for now.
+
+   - Typically, you would write a short description of the changes here, but now we have Copilot to help out!
+
+1. To the right of the **Message** text box, find and click the **Generate Commit Message with Copilot** button (sparkles icon).
+
+1. Press the **Commit** button and **Sync Changes** button to push your changes to the `modernize-legacy-code`branch on GitHub.
+
+1. Wait a moment for Mona to check your work, provide feedback, and share the next lesson.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+If you don't get feedback, here are some things to check:
+
+- Make sure your pushed the `docs/README.md` file changes to the branch `modernize-legacy-code`.
+
+</details>

.github/steps/2-explain-legecy-code.md

@@ -0,0 +1,68 @@
+## Step 2: Run the COBOL application and create a test plan to ensure quality of our legacy codebase
+
+In the following activies we will build and run the COBOL accounting application and create a test plan that we can use to ensure the quality of our legacy codebase.
+
+### ⌨️ Activity: Build and run the COBOL application
+
+1. Compile the COBOL source code using the appropriate compiler.
+1. Execute the compiled program with sample input data.
+1. Observe the output and verify it against expected results.
+
+ > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
+  >
+  > ```prompt
+  > @workspace Using our custom Copilot instructions, please build and run the COBOL application using the provided source code and sample data. Make sure the application is in the root of the repository with the name accountsystem.
+  > ```
+
+Try playing with the different options of the COBOL accounting app and when you are done select option `4` to exit.
+
+### ⌨️ Activity: Generate a test plan to validate the current implementation
+
+Given the features of our existing legacy accounting system we want to generate a comprehensive test plan that covers all critical functionalities and edge cases.
+
+  > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
+  >
+  > ```prompt
+  > @workspace The current Cobol app has no tests. Can you please create a test plan of the
+  > current business logic that I can use to validate with business stakeholders about the current implementation in a file called docs/TESTPLAN.md.
+  >  Later I would like to use this test plan to create unit and integration tests in a node.js app. I am in the middle of transforming the current Cobol app to a node.js app.
+  > The test plan should include the following headings:
+  > 1. Test Case ID
+  > 2. Test Case Description
+  > 3. Pre-conditions
+  > 4. Test Steps
+  > 5. Expected Result
+  > 6. Actual Result
+  > 7. Status (Pass/Fail)
+  > 8. Comments
+  >
+  > Please create the test plan in a markdown table format. The test plan should cover all the business logic in the current Cobol app.
+  >
+  > ```
+
+Make sure you can preview the test plan in the `docs/TESTPLAN.md` file.
+
+1. In the left sidebar, select the `Source Control` tab and make sure you are making changes on `modernize-legacy-code`branch.
+
+   > **Tip:** Opening a file from the source control area will show the differences to the original rather than simply opening it.
+
+1. Find the `docs/TESTPLAN.md` file and press the `+` sign to collect your changes together in the staging area.
+
+1. Above the list of staged changes, find the **Message** text box, but **don't enter anything** for now.
+
+   - Typically, you would write a short description of the changes here, but now we have Copilot to help out!
+
+1. To the right of the **Message** text box, find and click the **Generate Commit Message with Copilot** button (sparkles icon).
+
+1. Press the **Commit** button and **Sync Changes** button to push your changes to the `modernize-legacy-code`branch on GitHub.
+
+1. Wait a moment for Mona to check your work, provide feedback, and share the next lesson.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+If you don't get feedback, here are some things to check:
+
+- Make sure your pushed the `docs/TESTPLAN.md` file changes to the branch `modernize-legacy-code`.
+
+</details>