chore: update VC-04 status — credential issuance error investigation needed

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Dorian 2026-03-14 05:29:45 +00:00
parent e84c5e7a78
commit 1dc9f1f187

View File

@ -283,7 +283,7 @@ Every test must pass **10 consecutive times** from BOTH .228→.198 AND .198→.
- [x] **VC-03** — Added VC verification status to federation.list-nodes. Each node includes `vc_verified: bool` — true if a non-revoked FederationTrustCredential exists for that node's DID. VC-02 issues these during federation.join. (Full presentation exchange deferred.) - [x] **VC-03** — Added VC verification status to federation.list-nodes. Each node includes `vc_verified: bool` — true if a non-revoked FederationTrustCredential exists for that node's DID. VC-02 issues these during federation.join. (Full presentation exchange deferred.)
- [ ] **VC-04** — (BLOCKED: .198 backend keeps crashing/restarting — 502 errors during tests. VC flow requires both nodes stable simultaneously. .228 VC issuance/verification works in isolation via test-all-features.sh. Cross-node VC exchange needs .198 stability fix.) - [ ] **VC-04** — (BLOCKED: identity.issue-credential returns "Operation failed" on .228. Error sanitization hides the real error. Both nodes stable now. Credentials directory exists with credentials.json. Identity records exist. The signing callback in credentials.rs may be failing. Needs error logging investigation — the `error!()` macro output isn't appearing in journalctl despite tracing level set to debug.)
--- ---