SubmitFleet engine foundation (PRD v2.0)

[ralyodio]

Implements the engine described in the SubmitFleet PRD v2.0 (2026-10-14). This is the foundation the 100-destination release is measured against, not that release.

Honest status

• Release-qualifying destinations: 0 / 100 (submitfleet coverage report exits 3)
• Adapters: 1 (TinyLaunch), contract-tested against https://www.tinylaunch.com/llms.txt; no live submission made
• Nothing deployed; no DNS, accounts or third-party submissions touched

What's in it

• Release gate (PRD §4): staged qualification (discovered → source-labeled free → verified free → permission reviewed → live tested → release qualifying). Counts independent listing groups only; aliases, mirrors, assisted, always-captcha, social/newsletter and backlink routes never count. Imports can't enable execution.
• Strict campaigns: default min_executable_destinations: 100; below that → coverage_insufficient with the real count and blockers, and no writes.
• Approvals bound to a scope hash (targets, accounts, payloads, product facts, dates, spend). Material change invalidates. No agent/MCP path grants approval; CLI approves only from an interactive TTY.
• Durable execution: intents persisted before writes; atomic leased claims with fencing; per-account queue limits/cooldowns enforced inside the claim; timeout ⇒ uncertain ⇒ reconcile before retry; append-only event log; atomic budget reservations; global/campaign pause, account disconnect, destination disable.
• Surfaces: Hono /api/v1, MCP (stdio + Streamable HTTP at /mcp, submitfleet_ tools, list cache fields), CLI with stable exit codes + doctor, TUI, mobile dashboard at /app with Copy Markdown + clipboard fallback, /install.sh.
• Reports: Markdown/JSON/CSV; unknown analytics/effort stay null.

Tests

48 vitest tests mapped to the PRD §16 acceptance list (1-20) plus TinyLaunch contract tests. CLI, HTTP and MCP stdio smoke-tested end to end locally.

Known gaps

See README "Known gaps against the PRD": 99+ adapters and live evidence, URL fact extraction, magic-link/passkey dashboard auth, Next dashboard, browser-adapter runtime, analytics provider, hosting/DNS.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vitest@​5.0.4
	@​types/​node@​26.6.5
	tsx@​4.23.15
	@​libsql/​client@​0.18.0
	typescript@​7.0.2
	@​hono/​node-server@​2.1.5
	zod@​4.6.7
	hono@​4.13.13
	@​modelcontextprotocol/​sdk@​1.32.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	License policy violation: npm @typescript/typescript-aix-ppc64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-aix-ppc64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-aix-ppc64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-darwin-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-darwin-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-darwin-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-darwin-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-darwin-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-darwin-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-freebsd-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-freebsd-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-freebsd-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-freebsd-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-freebsd-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-freebsd-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-arm under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-arm@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-arm@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-loong64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-loong64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-loong64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-mips64el under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-mips64el@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-mips64el@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-ppc64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-ppc64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-ppc64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-riscv64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-riscv64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-riscv64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-s390x under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-s390x@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-s390x@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-linux-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-linux-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-linux-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-netbsd-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-netbsd-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-netbsd-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-netbsd-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-netbsd-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-netbsd-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-openbsd-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-openbsd-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-openbsd-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-openbsd-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-openbsd-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-openbsd-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-sunos-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-sunos-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-sunos-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-win32-arm64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-win32-arm64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-win32-arm64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm @typescript/typescript-win32-x64 under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: pnpm-lock.yaml → npm/typescript@7.0.2 → npm/@typescript/typescript-win32-x64@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript/typescript-win32-x64@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	License policy violation: npm typescript under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (package/NOTICE.txt) From: package.json → npm/typescript@7.0.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report