chore(m3): CodeRabbit CHANGELOG nits + CI anchor build log artifact

[graveyieldprotocol]

Summary

Two small follow-ups before m5 work begins.

1. CHANGELOG.md fixes (CodeRabbit's 2 nits from PR #15)

Both findings were minor 🟡 doc-accuracy issues, no code defects. Addressed:

• init_if_needed Anchor feature entry rewritten to describe what actually shipped: Anchor 0.32-compatible lazy init via manual system_program::create_account CPI. PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates #12's original init_if_needed design was incompatible with Anchor 0.32's new "Cannot use init on SystemAccount" check, and PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates (rebased) #15 already replaced it — the CHANGELOG just hadn't caught up.
• lp_holder_pool_vault migration entry split into two cases:
  • claim_lp_proceeds: SystemAccount (read-only path, safe under 0.32)
  • salvage_pool: UncheckedAccount + manual CPI (CodeRabbit's specific suggestion)
• Verification status updated from "cargo check not yet run" to the actual local results that gated PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates (rebased) #15's merge (fmt, clippy, 20/20 tests, BPF compile). Plus an explicit note that CI's anchor build job is currently failing and is being tracked.

2. CI workflow gains anchor-build log artifact upload

The current CI workflow runs anchor build and on failure the only diagnostic surface is the GitHub Actions web UI log page. The Composio integration this repo uses for programmatic CI inspection does not expose log download (verified across multiple action names — all return "not available"). So debugging the post-PR-#15 anchor build regression has been blind.

This PR teases anchor build's stdout/stderr to /tmp/anchor-build.log and adds an actions/upload-artifact@v4 step that runs if: failure(). After this PR lands and a future CI run fails on anchor build, the log artifact will be downloadable for offline diagnosis.

Why two changes in one PR

Both are small, neither touches program source, and the anchor build log artifact is the diagnostic mechanism we'll use to unblock m5 work. Keeping them together avoids two trivial PRs.

Verification

No source changes. Locally on rust 1.91.1 + anchor 0.32.1 + solana 3.0.10 + platform-tools v1.54:

• CHANGELOG.md renders correctly (Markdown syntax preserved)
• ci.yml: valid YAML, no behavior change other than added tee + artifact upload
• cargo fmt / clippy / tests / cargo-build-sbf: still clean (no source touched, but verified the working tree)

Test plan

• CI runs on this PR. anchor build should still fail (same root cause as PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates (rebased) #15) — but this time the log artifact will be uploaded.
• Download anchor-build-log artifact via GitHub Actions UI or API.
• Analyze actual failure cause.
• Open a separate fix PR addressing the actual issue.

Refs

• PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates (rebased) #15: m3 merge that surfaced the CHANGELOG nits + anchor build failure
• CodeRabbit review on PR feat(grave-vault): m3 salvage_pool pre-flight + cert freshness gates (rebased) #15: 2 line-level comments on CHANGELOG.md lines 37 + 83

Summary by CodeRabbit

• Chores

  • Enhanced CI workflow to capture full build logs and upload them as artifacts when failures occur, enabling improved failure diagnostics with automatic 7-day retention policy.

• Documentation

  • Updated release documentation for v1.0.6 milestone 3 with refined implementation details, account handling clarifications, and comprehensive verification status from local and CI environments.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 631c0a09-83bc-433b-96d3-c4a2f6fc1445

📥 Commits

Reviewing files that changed from the base of the PR and between 4cdd1a9 and 67011c2.

📒 Files selected for processing (2)

• .github/workflows/ci.yml
• CHANGELOG.md

---

📝 Walkthrough

Walkthrough

This PR adds CI build-log capture for failure diagnostics and updates CHANGELOG.md to document the Anchor 0.32-compatible lazy vault initialization approach, refine account-type handling, and report verified local build results plus the current CI IDL generation failure.

Changes

Build Infrastructure and Verification

Layer / File(s)	Summary
CI Build Logging .github/workflows/ci.yml	The anchor-build job output is now piped through tee to capture logs to /tmp/anchor-build.log, with a new conditional step that uploads the log as a anchor-build-log artifact on job failure with 7-day retention for improved diagnostics.
Implementation and Verification Documentation CHANGELOG.md	Implementation details are clarified: lazy vault initialization uses a manual create_account CPI when the PDA has zero lamports (Anchor 0.32 compatible), replacing the prior init_if_needed approach. Account types are refined: claim_lp_proceeds uses SystemAccount while salvage_pool uses UncheckedAccount with PDA seed validation. Verification status is updated with concrete local test and build timing results, and notes the specific CI failure at the post-cargo-build-sbf IDL generation phase.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A log to catch the build that breaks,
And docs to show what each one makes—
Lazy vaults dance in CPI light,
While changelog charms make futures bright! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately summarizes both main changes: CHANGELOG updates and CI artifact logging for anchor build failures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/m3-followups

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}