follow stricter output format

[mdtux89]

No description provided.

[junie-github-actions]

Junie successfully finished!

Result: Review PR Diff and Update Documentation Accuracy

Documentation Review Complete ✅

After reviewing the PR diff for the stricter-format branch and comparing it with the existing documentation, I can confirm that the README.md and COOKBOOK.md are accurate and up-to-date. No documentation updates are required.

Summary of Findings:

PR Changes Analyzed:

• The PR modifies src/constants/github.ts to add structured output format requirements to two internal prompt functions:
  • getCiFixPrompt(): Now requires specific markdown templates ("✅ CI Fix Applied" or "⚠️ CI Analysis")
  • getMinorFixPrompt(): Now requires specific markdown templates ("✅ Minor Fix Applied" or "⚠️ Minor Fix Not Applied")
• These changes add the instruction "DO NOT post inline comments" to both prompts

Documentation Status:

1. action.yml inputs/outputs: All correctly documented in README.md ✓
2. Code examples: All workflow examples in README.md and COOKBOOK.md are correct ✓
3. Feature documentation: Both fix-ci and minor-fix features are properly documented:
   • README.md mentions them in Features section and prompt input description
   • COOKBOOK.md has detailed sections with complete workflow examples
4. Configuration examples: All match the actual implementation ✓

Why No Updates Are Needed:

The PR changes are internal implementation details that improve the consistency and structure of Junie's output format. They don't affect:

• User-facing API or configuration
• Input parameters or output values
• How users interact with the action
• Workflow setup or usage patterns

The existing documentation appropriately describes these features at a high level (e.g., "implements fixes automatically", "quickly implement small PR adjustments"), which is the correct level of detail for user-facing documentation. The specific output format templates are internal guidelines for Junie's behavior and don't need to be documented in user guides.