Skip to content
This repository was archived by the owner on Mar 9, 2026. It is now read-only.

chore: rename boundary-validator LICENSE.txt to LICENSE#71

Merged
roottool merged 1 commit intomainfrom
chore/rename-boundary-validator-license
Mar 5, 2026
Merged

chore: rename boundary-validator LICENSE.txt to LICENSE#71
roottool merged 1 commit intomainfrom
chore/rename-boundary-validator-license

Conversation

@roottool
Copy link
Copy Markdown
Owner

@roottool roottool commented Mar 5, 2026

Description

Remove the .txt extension from skills/boundary-validator/LICENSE.txt to match the repository root convention (LICENSE has no extension).

Type of Change

  • Bugfix (non-breaking change fixing an issue)
  • Security fix (non-breaking change addressing a security issue)
  • Documentation (changes to documentation only)
  • Refactoring (non-breaking change improving code structure)
  • Tests (adding or updating tests)
  • Tooling / CI (changes to build tools, CI configuration)

Boundary Checklist

  • This is a non-implementation change (Documentation, Tooling, or CI only)
  • No interpretation — Keys treated as opaque strings, no structural inference
  • No silent behavior — No merging, overwriting, or implicit resolution
  • Boundary respected — No validation, coercion, or business logic

📘 AGENTS.md

Security & API Stability

  • No security impact (forbidden keys, prototype safety unaffected)
  • No changes to public API (parse, ParseResult, ParseIssue, IssueCode)
  • No breaking changes; or justified with version bump rationale
  • Compatible with current v0.x versioning policy

Testing

  • bun run check:type:source passes
  • bun run test passes
  • bun run build passes

Signature

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

@roottool roottool self-assigned this Mar 5, 2026
@roottool roottool merged commit a632cc5 into main Mar 5, 2026
@roottool roottool deleted the chore/rename-boundary-validator-license branch March 5, 2026 16:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant