Implement scripts, workflows, and infrastructure per README specifications

[Copilot]

Implementation Plan: CTF-Kit README Guidelines

Based on the README review, I need to implement the following:

Scripts Directory Structure

• Create scripts/Networking/ subdirectory
• Create scripts/Enumeration/ subdirectory
• Implement basic_nmap_scan.sh in Networking
• Implement advanced_nmap_scan.sh with NSE in Networking
• Implement web_server_enum.sh in Enumeration
• Implement smb_share_enum.sh in Enumeration
• Add README documentation for Networking scripts
• Add README documentation for Enumeration scripts

GitHub Actions Setup

• Create workflow for PR automation
• Create workflow for branch management
• Add contribution validation workflow
• Add auto-labeling workflow
• Add contributor greeting workflow
• Add explicit permissions to workflows (security)
• Fix labeler.yml configuration for v5 format

Additional Infrastructure

• Create .gitignore file for common CTF artifacts
• Create CONTRIBUTING.md guide
• Create PR template
• Configure labeler for automatic PR labeling

Documentation Enhancements

• Create comprehensive docs README with navigation
• Verify all docs are properly linked
• Ensure all challenge types docs are complete
• Address code review feedback

Security

• Run CodeQL security scan
• Fix all security vulnerabilities

All tasks completed! The repository now fully implements what's described in the README with proper security measures and working GitHub Actions.

Original prompt

Please review the README and implement what's described throughout the codebase

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[cywf]

@copilot please fix the Auto Label PRs workflow failure by correcting the .github/labeler.yml configuration.

Here’s the issue context:

• The workflow log shows: Error: found unexpected type for label 'documentation' (should be array of config options)
• This means the documentation label (and possibly others) is not formatted as an array, which the GitHub Labeler Action requires.

Actions to perform:

1. Open .github/labeler.yml
2. Ensure every label uses array syntax — even if it has only one rule.
3. Specifically, change entries like this:

   documentation: docs/

to:

documentation:
  - docs/

4. Review the rest of the file and fix any other labels that are not arrays, for example:

workflows: .github/workflows/

should become:

workflows:
  - .github/workflows/**

5. Validate the YAML structure for proper indentation (2 spaces per level) and ensure all keys use : followed by a newline when listing multiple patterns.

6. Commit the corrected file with this message:

7. fix: correct labeler.yml array syntax for GitHub Auto Label workflow
   Re-run the workflow to confirm the Auto Label PRs / label job passes.

[Copilot]

@copilot please fix the Auto Label PRs workflow failure by correcting the .github/labeler.yml configuration.

Here’s the issue context:
...

Fixed in commit 661fa24. Updated .github/labeler.yml to use the correct v5 format with changed-files and any-glob-to-any-file structure required by actions/labeler@v5.