Why: The product needs the new content rules and the optional squad entry, while the library pins must match the kernel and router those paths compile against. Evidence: Backend go test ./... -count=1 passed on 268f4a9. runtime.entry stays direct because no paired live scores exist. Impact: Dev now points at the quality and squad-entry backend, agent-native cfc840c, and agent-squad d38f838. make eval-deliverables runs the scorecard tests. Refs: deliverable-quality-system Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -84,6 +84,9 @@ test-core:
|
||||
test-backend:
|
||||
cd $(BACKEND) && go test ./...
|
||||
|
||||
eval-deliverables:
|
||||
cd $(BACKEND) && go test ./eval/ ./internal/quality/ -count=1
|
||||
|
||||
test-frontend: contracts
|
||||
cd $(FRONTEND) && npm ci --no-fund --no-audit && npx vitest run
|
||||
|
||||
|
||||
Vendored
+1
-1
Submodule deps/agent-native updated: f9ab2ef698...cfc840c11d
Vendored
+1
-1
Submodule deps/agent-squad updated: 9a402e468e...d38f838dbc
+1
-1
Submodule modules/backend updated: 2079b2dfa8...268f4a9abf
Reference in New Issue
Block a user