update copilot instructions with AI compliance workflow (#353)

Signed-off-by: Rishi Kumar Chawda <rishichawda@users.noreply.github.com>

Author: rishichawda

.github/copilot-instructions.md

@@ -57,7 +57,8 @@ When a Jira ID is provided, use the **atlassian-mcp-server** to:
 
 ### 2. Implementation Process
 
-#### Step-by-Step Workflow:
+#### Step-by-Step Workflow
+
 1. **Analysis Phase**
    - Fetch and analyze Jira issue details
    - Review existing code and tests
@@ -89,13 +90,15 @@ When a Jira ID is provided, use the **atlassian-mcp-server** to:
 ### 3. Testing Requirements
 
 **Mandatory Testing Standards:**
+
 - Minimum 80% test coverage required
 - Unit tests for all new functionality using RSpec
 - Integration tests using oc-pedant when applicable
 - Test both success and error scenarios
 - Mock external dependencies appropriately
 
 **Test Commands:**
+
 ```bash
 # Run unit tests
 rake spec
@@ -162,6 +165,7 @@ EOF
 ### 6. Build System Integration
 
 **Expeditor Build System:**
+
 - Automatic version bumping on merge
 - Changelog generation
 - Gem publishing to RubyGems
@@ -172,6 +176,7 @@ EOF
   - `Expeditor: Skip Changelog`
 
 **GitHub Workflows:**
+
 - `ci-main-pull-request-checks.yml`: Main CI pipeline
 - `unit-test.yml`: Unit test execution
 - `lint.yml`: Code style checking
@@ -180,6 +185,7 @@ EOF
 ### 7. Repository-Specific GitHub Labels
 
 **Aspect Labels:**
+
 - `Aspect: Documentation`: Documentation-related changes
 - `Aspect: Integration`: Integration with other systems
 - `Aspect: Packaging`: Distribution and packaging
@@ -193,26 +199,30 @@ EOF
 - `Aspect: UX`: User experience improvements
 
 **Platform Labels:**
+
 - `Platform: AWS`, `Platform: Azure`, `Platform: GCP`
 - `Platform: Linux`, `Platform: macOS`
 - `Platform: Debian-like`, `Platform: RHEL-like`, `Platform: SLES-like`
 - `Platform: Docker`
 
 **Special Labels:**
+
 - `dependencies`: Dependency updates
 - `oss-standards`: OSS standardization
 - `hacktoberfest-accepted`: Hacktoberfest contributions
 
 ### 8. Prompt-Based Development
 
 **After each step, provide:**
+
 1. Summary of completed work
 2. Current status
 3. Next step in the process
 4. Remaining steps overview
 5. **Ask for confirmation to continue**
 
 Example prompt:
+
 ```
 ✅ Completed: Analysis of Jira issue JIRA-123 and identified required changes
 📍 Current: Ready to implement feature in lib/chef_zero/endpoints/
@@ -225,6 +235,7 @@ Would you like me to proceed with the implementation phase?
 ### 9. Prohibited Modifications
 
 **DO NOT modify these files without explicit approval:**
+
 - `VERSION` file (managed by Expeditor)
 - `.expeditor/config.yml` (build configuration)
 - Core gemspec metadata
@@ -234,6 +245,7 @@ Would you like me to proceed with the implementation phase?
 ### 10. Code Style and Conventions
 
 **Ruby Style Guidelines:**
+
 - Follow RuboCop/Cookstyle conventions
 - Use 2-space indentation
 - Maximum 120 characters per line
@@ -242,6 +254,7 @@ Would you like me to proceed with the implementation phase?
 - Add appropriate error handling and logging
 
 **Chef Zero Specific Patterns:**
+
 - Inherit from `RestBase` for new endpoints
 - Use appropriate HTTP status codes
 - Follow existing JSON response formats
@@ -299,6 +312,52 @@ gh pr create --title "Title" --body "Description with HTML tags"
 - Ensure DCO compliance for all contributions
 - Maintain compatibility with Chef Client versions 11+
 
+## AI-Assisted Development & Compliance
+
+- ✅ Create PR with `ai-assisted` label (if label doesn't exist, create it with description "Work completed with AI assistance following Progress AI policies" and color "9A4DFF")
+- ✅ Include "This work was completed with AI assistance following Progress AI policies" in PR description
+
+### Jira Ticket Updates (MANDATORY)
+
+- ✅ **IMMEDIATELY after PR creation**: Update Jira ticket custom field `customfield_11170` ("Does this Work Include AI Assisted Code?") to "Yes"
+- ✅ Use atlassian-mcp tools to update the Jira field programmatically
+- ✅ **CRITICAL**: Use correct field format: `{"customfield_11170": {"value": "Yes"}}`
+- ✅ Verify the field update was successful
+
+### Documentation Requirements
+
+- ✅ Reference AI assistance in commit messages where appropriate
+- ✅ Document any AI-generated code patterns or approaches in PR description
+- ✅ Maintain transparency about which parts were AI-assisted vs manual implementation
+
+### Workflow Integration
+
+This AI compliance checklist should be integrated into the main development workflow Step 4 (Pull Request Creation):
+
+```
+Step 4: Pull Request Creation & AI Compliance
+- Step 4.1: Create branch and commit changes WITH SIGNED-OFF COMMITS
+- Step 4.2: Push changes to remote
+- Step 4.3: Create PR with ai-assisted label
+- Step 4.4: IMMEDIATELY update Jira customfield_11170 to "Yes"
+- Step 4.5: Verify both PR labels and Jira field are properly set
+- Step 4.6: Provide complete summary including AI compliance confirmation
+```
+
+- **Never skip Jira field updates** - This is required for Progress AI governance
+- **Always verify updates succeeded** - Check response from atlassian-mcp tools
+- **Treat as atomic operation** - PR creation and Jira updates should happen together
+- **Double-check before final summary** - Confirm all AI compliance items are completed
+
+### Audit Trail
+
+All AI-assisted work must be traceable through:
+
+1. GitHub PR labels (`ai-assisted`)
+2. Jira custom field (`customfield_11170` = "Yes")
+3. PR descriptions mentioning AI assistance
+4. Commit messages where relevant
+
 ---
 
 *This document should be updated as the project evolves and new requirements emerge.*