[jinxiao]

Issue

Closes #33

Summary

Default Bug report to the existing red bug label and Feature proposal to enhancement. Previously both forms omitted category labels. Document explicit labels for CLI-created issues; the eleven historical unlabeled bug issues have been backfilled.

Testing

• All 18 offline contribution/form regressions and whitespace checks passed.
• GitHub's label-add responses confirmed bug with color d73a4a for issues [Bug]: Logger children promote temporary attributes into persistent keys #3, [Bug]: Logger emits empty top-level attributes that the TypeScript formatter omits #4, [Bug]: Logger buffer ignores trace changes and omits overflow error details #5, [Bug]: Release fixture cleanup races detached Git maintenance on hosted CI #13, [Bug]: Dispatched release checks do not satisfy required PR rulesets #17, [Bug]: Publication looks up draft Releases using a published-only tag endpoint #19, [Bug]: Release publication reads newly created drafts before they are visible #20, [Bug]: Signer transport closes a shared request body before the base transport finishes #25, [Bug]: Base64Encoded disagrees with pinned UTF-8 replacement and BOM decoding #26, [Bug]: Parameter transforms collapse malformed UTF-8 and fail BOM-prefixed byte JSON #27, and [Bug]: Powertools Base64 functions collapse consecutive malformed UTF-8 subparts #28.
• All four native required PR checks passed: contribution policy, documentation, packaged modules, and Runtime simulation. Hosted Go CI: https://github.com/rambow-cloud/powertools-lambda-go/actions/runs/37244098396. CGO remained disabled; no AWS cloud tests were run.

Risks and compatibility

No Go API, dependency, or release-version changes. CLI/API creation must still supply the label explicitly. Release and task forms keep their existing defaults.

Release notes

• repository | maintenance | Automatically classify bug reports and feature proposals with standard category labels.

Checklist

• The issue records the scope and acceptance criteria
• Tests and documentation match the change
• I kept CGO disabled and did not run cloud AWS tests
• I excluded credentials and generated artifacts