Update to Vaquill AI Primary Law

{
  "description": "Track a Federal Register rulemaking: what an agency proposed, what became final, and when comments close. Subject: <topic or agency> [proposed|final] [since YYYY-MM-DD].",
  "included_files": [],
  "name": "rulemaking",
  "skill_md_contents": "---\nname: rulemaking\ndescription: Track a Federal Register rulemaking: what an agency proposed, what became final, and when comments close. Subject: <topic or agency> [proposed|final] [since YYYY-MM-DD].\n---\n\nTrack rulemaking whichever subject the conversation is about. If it is not clear from the conversation, ask for it before calling anything.\n\nThis is a different question from \"what does the law say\". The CFR is the rule in force; the Federal Register is the rule *moving*. Use `corpusType: \"FEDERAL_REGISTER\"`.\n\n## Filters that only work here\n\n- `agency` takes the FR agency slug, e.g. `environmental-protection-agency`. A list matches any of several. Combined with a non-FR corpus it returns **empty**, not an error.\n- `documentType` is `final`, `proposed` or `presidential`. Ask which the user means: \"what did EPA do\" is usually final, \"what is coming\" is proposed.\n- `publishedFrom` / `publishedTo` are the **publication** date. This is not `yearFrom`, which filters a section's version year.\n\nEach result carries `agencySlugs`, and those are exactly the values `agency` accepts, so a facet round-trips straight back into a narrower query.\n\n## Report the dates carefully, because there are four of them\n\n| Field | Meaning |\n| --- | --- |\n| `publicationDate` | When it appeared in the Register |\n| `frEffectiveOn` | When the rule takes effect |\n| `frCommentsCloseOn` | The comment deadline on a proposed rule |\n| `datesText` | The publisher's own prose, ~98% populated |\n\n**Prefer `datesText` when a rule has staged or conditional effective dates.** The single `frEffectiveOn` flattens that away, and a compliance reader acting on the flattened date can be wrong about when an obligation starts.\n\nA rule is routinely published well before it is effective. Never report `publicationDate` as when the rule took effect.\n\n## Follow the rulemaking, not just the document\n\nA single rulemaking is usually several documents: a proposed rule, its final rule, and any corrections. They are joined by the **Regulation Identifier Number**.\n\n`frRelatedDocuments` groups them, but it is **only populated on `get_us_statute_section`**, never on a search result, because computing it needs a follow-up lookup. So: search to find one document, then fetch it by `act_id` to see the rest of its family.\n\nAlso useful: `frRegulationIdNumbers` (the RIN itself), `frDocketIds`, `frCorrectionOf` and `frCorrections`, `frRegulationsDotGovUrl` for the comment docket, and `frStartPage`/`frEndPage`, which give the page range the citation cannot express.\n\n## Notices are a curated slice, not the whole series\n\n`FEDERAL_REGISTER_NOTICE` is a separate token holding roughly 2.4% of notices: the ones that act on a rulemaking (withdrawals, comment-period extensions and reopenings, significant guidance, negotiated rulemaking). Every notice carries `frNoticeClass` saying which rule admitted it.\n\nPaperwork Reduction Act collections, meeting notices and permit applications are **not held**. If the user is looking for one of those, say so rather than reporting an empty result as an absence.\n\n## Report\n\nGroup by rulemaking, not by document. For each: agency, stage, citation, publication date, the effective or comment-close date, and the `abstract` (populated on 99.9% of rules) rather than your own summary. Note `action` verbatim, since \"interim final rule\", \"direct final rule\" and \"withdrawal\" are legally different things.\n"
}