Get the actions for a project. status is suggested (DevTune proposed it, nobody has decided), accepted (the team wants it done), live (the page is published and its measurement window is open) or archived (taken off the queue by the team); blocked is true on accepted work the team has marked blocked. Suggested actions expose the same nullable opportunity percentile, percentileStatus and percentileScope as REST (signal_family compares like signals; families are interleaved), Reach, Gap, Confidence, family (including citation defence), estimated state, measured facts, and locked-page steering source. A null percentile carries percentileStatus insufficient_reach when reach is null, sensor coverage is absent, or estimated reach is zero. It carries percentileStatus no_measured_gap when every product in the family is zero and reach is non-null and not estimated-zero. Numeric percentiles omit the status. percentilePoolSize counts rankable candidates in the full family before selection or pagination. A size of one means Only ranked opportunity of this type, never Top 1%. Older records omit the pool size; do not infer singleton status from percentile 100 or the returned page. Positive-product candidates are seated before zero-product candidates. Citation-defence normalization is matched_cohort_executions when the cohort rollup is published or window_executions when the matched cohort is not published yet. Both compare citations per successful prompt execution; matched-cohort loss reports one-window-only composition changes and states matched coverage of earlier citations. Suggested actions come first and follow persisted portfolioRank ascending, nulls last, and no action exposes a legacy scalar score. Context detail includes interventionExplanation, the same stored page decision as the app and REST, or null for legacy/manual rows without a shape. It includes selectedMove, buyerQuestions, source, auditFindings, nearby alternative and reason, limitations, protectedPageUrls and human_review_required approval. A recorded question can have null retained text; this does not mean no question was tracked. Refactor reorganizes an existing answer; enrich adds missing or outdated detail, both using refresh storage. Read stored_snapshot as unvalidated against current pages/questions, even for accepted, live or restored actions. Retargeting and consolidation are not selected moves: the stored evidence does not establish a new target question or justify combining pages. Limitations report only gaps relevant to the action; Creation is the stored choice, not a measurement that no existing page fits. Preserve unique facts and distinct intent; never delete pages or change protected pages. No edits, redirects or relinks have executed. Context metrics may include ownedPageMatches (at most forty) and ownedPageMatchCount (total retained checks). A no_match covers only the at-most-twelve-page shortlist; coverageIssues records unjudged inventory limits and source failures. It never proves that no page exists elsewhere. An incomplete check is not negative evidence, and checkedAt is omitted for an unstarted or undated check. Context detail includes topEvidence.redirectTargets for missing-page demand: up to three existing same-site URL and title candidates to check before redirecting, or an empty list. Candidates never change the action rank. Context detail includes bounded audit assessment dates, factor checks and prompt-coverage limits, plus structured Google eligibility dimensions when entitled live evidence is available. Every action carries assignedTo (its owner's user id, null when unassigned) and ownerName; change either with devtune_update_action. followUpOf (actionId, title, shippedAt) names the earlier action that shipped this page, null when there is none; read its result from the outcomes ledger. The intervention explanation records the original stored recommendation; current brief motion and the offered drafter take precedence when the brief chooses another approach. Question and Audit-finding lists disclose truncation through buyer_questions_truncated and audit_findings_truncated limitations. Context detail lists mergedSuggestions (label, mergedAt, confidence): reworded suggestions the duplicate check merged into the action as the same fix, hidden from the queue while the action holds its decision. Splitting one back out is done on the action's page in the app; this tool cannot split. Context detail includes robotsTxtDraftSummary for an Audit-finding action whose robots.txt blocks an answer engine or AI search crawler: whether an edit was drafted, the crawler tokens it unblocks and when the audit read the file, or null. Read the edited file and diff with devtune_get_action_brief. A human applies the edit; nothing has been applied, and training crawlers are never unblocked.