Refactor issue labeller workflow

- Deleted the old issue labeller markdown file and replaced it with a new version that includes updated formatting and structure.
- Updated README to correct the spelling of "labeler" and adjusted references to the job name in the workflow.
- Added a new lock file for the issue labeler workflow, detailing the steps and configurations for the GitHub Actions workflow.
- Enhanced the agentic output collection and logging mechanisms to improve clarity and functionality.
- Implemented a more robust label addition process, ensuring only allowed labels are applied based on agent output.

Author: pelikhan

.github/workflows/issue-labeller.lock.yml .github/workflows/issue-labeler.lock.yml.github/workflows/issue-labeller.lock.yml renamed to .github/workflows/issue-labeler.lock.yml

@@ -6,7 +6,7 @@ output:
   labels:
     allowed: [bug, feature]
 ---
-## Issue Labeller
+## Issue Labeler
 - analyze issue #${{ github.event.issue.number }} content
 - categorize the content as 'bug' or 'feature'
 - label the issue accordingly

.github/workflows/issue-labeller.md .github/workflows/issue-labeler.md.github/workflows/issue-labeller.md renamed to .github/workflows/issue-labeler.md

@@ -47,7 +47,7 @@ You can explore other samples at [githubnext/agentics](https://github.com/github
 
 ## 📝 Agentic Workflow Example
 
-Here's what a simple agentic issue labeller workflow. This example automatically labels an incoming issue.
+Here's what a simple agentic issue labeler workflow. This example automatically labels an incoming issue.
 The section between `---` at the start is called the frontmatter and contains a superset of GitHub Actions Workflow syntax.
 
 ```markdown
@@ -76,7 +76,7 @@ on:
   issues:
     types: [opened]
 jobs:
-  issue-labeller:
+  issue-labeler:
     permissions:
       contents: read # agent container only has read access
     outputs:
@@ -86,7 +86,7 @@ jobs:
       # run agent with markdown prompt
       # save outputs
   add_labels:
-    needs: issue-labeller
+    needs: issue-labeler # wait for agent results
     permissions:
       issues: write # write access to add labels
     steps: