diff --git a/.github/workflows/content-validation.yml b/.github/workflows/content-validation.yml
index 5b2a93a..a0f53cc 100644
--- a/.github/workflows/content-validation.yml
+++ b/.github/workflows/content-validation.yml
@@ -6,6 +6,11 @@ on:
   pull_request:
     types: [opened, edited, synchronize, reopened]
 
+permissions:
+  contents: read
+  pull-requests: write
+  issues: write
+
 jobs:
   validate-content:
     runs-on: ubuntu-latest
diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 0000000..5d40a8a
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,16 @@
+{
+  "name": "learning-room",
+  "version": "1.0.0",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "learning-room",
+      "version": "1.0.0",
+      "license": "CC-BY-4.0",
+      "engines": {
+        "node": ">=20.0.0"
+      }
+    }
+  }
+}
diff --git a/practice/chapter-4-1-create-issue.md b/practice/chapter-4-1-create-issue.md
new file mode 100644
index 0000000..b2ff49d
--- /dev/null
+++ b/practice/chapter-4-1-create-issue.md
@@ -0,0 +1,33 @@
+# Chapter 4.1: Create Your First Issue - Test Submission
+
+**Student:** Test User (@testuser)  
+**Challenge:** Chapter 4 - Working with Issues  
+**Task:** Create one issue with a clear title and short description
+
+## What I Learned
+
+I learned how to create an issue on GitHub with:
+- A clear, descriptive title
+- A concise description of what needs to be done
+- Proper formatting using markdown
+
+## My Practice Issue
+
+I created issue #1 requesting to add a new feature to the learning room documentation.
+
+The issue includes:
+- Title: "Add keyboard shortcuts guide"
+- Description: Brief explanation of what's needed
+- Labels: documentation, enhancement
+
+## Reflection
+
+Creating issues helps organize work and communicate clearly with team members. Good issue titles make it easier for everyone to understand what needs attention.
+
+---
+
+**Completion checklist:**
+- [x] Issue created with clear title
+- [x] Description provided
+- [x] Issue linked in this document
+- [x] Reflection written
diff --git a/practice/chapter-5-2-linked-pr.md b/practice/chapter-5-2-linked-pr.md
new file mode 100644
index 0000000..045058d
--- /dev/null
+++ b/practice/chapter-5-2-linked-pr.md
@@ -0,0 +1,26 @@
+# Chapter 5.2: Open a Linked PR - Test Submission
+
+This PR demonstrates linking to an issue using the Closes keyword.
+
+## What Changed
+
+Added documentation about creating issues in Chapter 4.
+
+## Issue Reference
+
+Closes #1
+
+## Testing Checklist
+
+- [x] Branch created from main
+- [x] Changes committed with clear message
+- [x] PR linked to issue using "Closes #XX"
+- [x] PR description includes what changed
+
+## Notes
+
+For more information about GitHub workflow, [click here](./nonexistent-file.md).
+
+![Project screenshot](./screenshot.png)
+
+You can [read more](https://example.com) about pull requests in the GitHub docs.