chore(workspace): implement comprehensive license policy enforcement and attribution generation

- Add license-checker-rseidelsohn for professional license analysis
- Create configurable license policy with allowed, prohibited, and review-required licenses
- Add automated license policy enforcement in pre-commit hooks
- Add comprehensive license analysis and reporting scripts
- Update documentation with license policy and procedures
- Add conventional commit guidelines to copilot instructions
- Enhance pre-commit hooks to check license compliance before attribution generation

Author: santi698

.github/copilot-instructions.md

@@ -66,3 +66,73 @@ nx codegen sdk         # Generate OpenAPI client for SDK
 - **Testing patterns**: `docs/TESTING_CONVENTION.md`
 - **Coverage requirement**: 85% threshold for both packages
 - **Test isolation**: Automatic mock cleanup between tests
+
+### Package Installation Policy
+
+Before installing any npm packages, always research and include information about:
+
+- **Maintenance state**: When was it last updated, frequency of releases
+- **Community health**: Open issues count, response time to issues, number of contributors
+- **License compatibility**: Verify license is compatible with our open source policy
+- **Security**: Check for known vulnerabilities or security advisories
+- **Alternatives**: Consider if there are better-maintained or more suitable alternatives
+
+## Commit Message Standards
+
+### Conventional Commits Format
+
+Use the [Conventional Commits](https://www.conventionalcommits.org/) specification:
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Commit Types
+
+- **feat**: New feature for SDK or CLI users (user-facing functionality)
+- **fix**: Bug fix for SDK or CLI users
+- **chore**: Maintenance, tooling, dependencies, build processes
+- **docs**: Documentation changes
+- **style**: Code style changes (formatting, missing semicolons, etc.)
+- **refactor**: Code changes that neither fix bugs nor add features
+- **test**: Adding or modifying tests
+- **ci**: CI/CD pipeline changes
+
+### Scoping Rules
+
+- **Single package changes**: Use package name as scope (`sdk`, `cli`)
+- **Monorepo tooling**: Use `workspace`, `build`, `deps`, or omit scope
+- **Documentation**: Use `docs` or specific area like `api-docs`
+
+### Examples
+
+```bash
+# User-facing features (only for SDK/CLI functionality)
+feat(sdk): add support for batch processing
+feat(cli): implement new auth command
+
+# Everything else is typically chore
+chore(deps): update dependencies to latest versions
+chore(workspace): add license checking and attribution generation
+chore(build): update tsconfig for better performance
+chore: setup automated testing pipeline
+
+# Bug fixes for users
+fix(sdk): resolve authentication timeout issue
+fix(cli): handle missing config file gracefully
+
+# Documentation
+docs(sdk): update API reference for new endpoints
+docs: add contributing guidelines
+```
+
+### Important Notes
+
+- **feat** is reserved for new user-facing functionality in SDK or CLI packages
+- Most tooling, build, and maintenance work should use **chore**
+- Always include scope when changes affect a single package
+- Keep descriptions concise and in present tense