docs: initialize SAPIENS value-analysis/create-epic commands

[s4piens]

Summary

• Adds SAPIENS command docs for /value-analysis and /create-epic
• Updates .sapiens/README.md to surface the new commands
• Converts .sapiens/tools to the filesystem backend config expected by the current SAPIENS flow

Notes

• No app code changes were made
• Existing unrelated working-tree changes were left untouched

[github-actions]

🔍 CI Check Results

Check	Status	Details
Python Lint (Ruff)	✅	Passed
TypeScript & ESLint	✅	Passed (non-blocking)
Build & Smoke Tests	✅	Passed

✅ All Required Checks Passed!

This PR is ready for review and can be merged.

---

Automated CI check • View workflow run

[s4piens]

Review indépendante — verdict : approve

The SAPIENS bootstrap docs are consistent with the new command layout, and the tool backend switch matches the stated workflow change.

🔴 Blocking : 0 · 🟡 Important : 0 · 🟢 Suggestion : 0

Points positifs

• The change is docs/config-only, so the blast radius is low.
• The commit set is internally coherent: docs and tool config move together.

Risques résiduels

• The PR does not include code-path verification because it is a documentation/bootstrap change.

Postée automatiquement. Aucun merge, aucune approbation : la décision reste humaine.

[s4piens]

Review indépendante — verdict : approve

The PR adds the new SAPIENS value-analysis/create-epic command docs and updates the tools manifest to the filesystem backend expected by the new flow. The change set stays confined to SAPIENS-facing metadata and documentation.

🔴 Blocking : 0 · 🟡 Important : 0 · 🟢 Suggestion : 0

Points positifs

• The PR keeps the scope narrow: it only updates SAPIENS bootstrap files and docs.
• The README and command docs are aligned, which reduces discoverability drift.
• The manifest change matches the new flow described in the PR body.

Risques résiduels

• Because the PR updates workflow metadata rather than app code, any downstream SAPIENS consumer that still expects the previous tools format would need to be updated in lockstep.

Postée automatiquement. Aucun merge, aucune approbation : la décision reste humaine.