adityamparikh opened a new pull request, #68:
URL: https://github.com/apache/solr-mcp/pull/68

   ## Summary
   
   - Introduces the full Spec Kit artifact set for the 
`001-graalvm-native-image` feature
   - **spec.md**: 3 user stories (< 1s startup, standard build pipeline, HTTP + 
OAuth2 mode); clarifications record the coexistence decision (`-native` tag 
suffix), the MCP hints answer (Spring AI's `McpHints` handles it — no custom 
hints needed), and confirmed that Spring Boot Buildpacks cannot replace Jib 
(CNB lifecycle launcher writes to stdout at runtime; no fix found as of March 
2026)
   - **plan.md**: 6 implementation phases (build infra → runtime hints → 
integration tests → CI → constitution amendment → docs), full Constitution 
Check (all 5 principles pass), and risk register
   - **research.md**: 8 key technical decisions including GraalVM 25, plugin 
0.11.4, Jib native image extension, `gcr.io/distroless/base-debian12` base 
image, multi-arch CI strategy (separate per-arch builds + manifest merge), and 
three-layer hint strategy
   - **contracts/**: build command interface (Gradle tasks, CI matrix) and 
Docker image runtime spec (env vars, transport modes, MCP tool surface)
   - **tasks.md**: 29 ordered tasks across 6 phases with parallel markers and 
critical path analysis
   
   ## Test plan
   
   - [ ] Review spec.md user stories and success criteria for completeness
   - [ ] Review plan.md Constitution Check — all 5 principles must be justified
   - [ ] Review research.md decisions, especially the multi-arch native build 
strategy and hint layer approach
   - [ ] Review tasks.md for correct task ordering and parallelism markers
   - [ ] Verify the Buildpacks research finding (CNB launcher stdout) is 
accurately recorded in spec.md Clarifications and Assumptions
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to