Is a ticket key in the branch enough?
Not by itself. Warestack resolves known identifiers in the PR title, branch, or body against the connected Linear workspace and persists successful matches. The rule passes only from that stored association, not from an unverified string. Check Warestack before reporting the link. Require concise pull requests (
pull_request.size_limit) is a different control.Can we link every PR to a Linear parent and use sub-issues only for planning?
Planning yes; association no. Warestack does not inherit a parent onto children. For a feature that spans repos, create a parent for the outcome and a sub-issue per independently reviewable PR, then associate each PR with that sub-issue. See How to ticket.
Do bot reviews count toward two approvals?
No. Bots and the pull request author do not count. Counting APPROVED reviews must also cite a named command, CI check, or environment result — not “LGTM.”
Does merge-blocking come on with the pack?
No. Leave it off until you have reviewed findings and ask to require Warestack Rules in branch protection. A failing check is not a gate by itself.
What happens if a merge-blocking rule cannot be evaluated?
Warestack fails closed. The GitHub check reports the blocking rule as unavailable and offers a rerun; an incomplete evaluation is never converted into a pass. Custom rules must have persisted checks, and every check needs a complete validated outcome.
Can we acknowledge a blocking finding?
A space admin can acknowledge an eligible finding in the console with a required reason. Warestack audits the action and refreshes the GitHub check. The acknowledgement applies only to that exact pull-request head revision and finding; a new head or materially changed finding reopens enforcement.
Why did Slack show Approved but still one High?
The live card updates as soon as GitHub records the review. Pull-request rules also re-run on review submit, review comments, and thread resolution. A High finding remains when the check still sees missing evidence (for example one human APPROVE when Require approvals by branch prefix needs two). Open the event timeline for the current snapshot.
I ran the weekly report. Why is Slack empty?
Run now revalidates and executes saved SQL. The Slack announce is the chain’s calendar step (for example Monday 09:00). See Digests.
Why is a report brief still queued or generating?
Briefs run asynchronously against an exact report-result snapshot.
queued and generating are progress states, not failures. Equivalent repeated requests are coalesced; regeneration creates a new version without overwriting the earlier brief.We merged. Why no changelog?
The changelog fires on GitHub deployment succeeded in
production/prod, after a short wait for associated PRs. Merge and environment approval (waiting) are not that event. See Production changelog.Can an admin enable someone else’s personal digest?
No. Each person enables it from Overview › Needs attention › Customize. It is not a report and not a repository chain.
Does the Linear agent invent a PR if none is linked?
No. It reports an empty snapshot and will not guess
owner/repo#n.Does Warestack replace Vanta?
No. Vanta stays GRC. Warestack runs the engineering control and leaves a sampleable trail. See SOC 2 and Vanta.
Can our org Claude or Codex design the pack from these docs?
Yes. Point it at this site, especially For AI agents and
/catalog.json. It should propose catalog IDs, not invent funnels. Without the MCP it cannot see Warestack’s association store. Connect Cursor, Claude, or Codex at mcp.warestack.com with the same GitHub account as the console.How do we connect Cursor, Claude, or Codex?
Open MCP. The production URL is
https://mcp.warestack.com/mcp . Sign in with GitHub. Slack and Linear OAuth stay in the console.Are chain kinds marked “later” unavailable?
No. Most are available in the create flow today. “Later” is first-enablement guidance. Review any default
block_merge or fail_check step before enablement.Last updated on