Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Search and read the NYC Charter, Administrative Code and Rules of the City of New York
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 19/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 31/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 18 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NYC Charter, Laws and Rules。按照 https://mcp.popnx.com/i/betanyc-nyc-charter-laws-rules.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server NYC Charter, Laws and Rules,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "nyc-charter-laws-rules": { "command": "npx", "args": [ "-y", "@betanyc/nyc-charter-laws-rules" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NYC Charter, Laws and Rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"nyc-charter-laws-rules": {
"command": "npx",
"args": [
"-y",
"@betanyc/nyc-charter-laws-rules"
]
}
}
}用 NYC Charter, Laws and Rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NYC Charter, Laws and Rules,或回答中出现 NYC Charter, Laws and Rules 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NYC_LAWS_INDEX_DIR 从此目录提供索引(结构与 data/index/json/ 相同),而非使用内置索引。 NYC_CLR_FOOTER 可选。每条回复附带的法律免责声明数量:先完整后精简(默认)或完整 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NYC Charter, Laws and Rules
NYC Charter, Laws and Rules 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 NYC Charter, Laws and Rules 的应用
B · 法律与政府数据 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server NYC Charter, Laws and Rules,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user nyc-charter-laws-rules -- npx -y @betanyc/nyc-charter-laws-rules 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NYC Charter, Laws and Rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user nyc-charter-laws-rules -- npx -y @betanyc/nyc-charter-laws-rules应能看到 NYC Charter, Laws and Rules 在列表中并显示已连接
用 NYC Charter, Laws and Rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NYC Charter, Laws and Rules,或回答中出现 NYC Charter, Laws and Rules 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NYC_LAWS_INDEX_DIR 从此目录提供索引(结构与 data/index/json/ 相同),而非使用内置索引。 NYC_CLR_FOOTER 可选。每条回复附带的法律免责声明数量:先完整后精简(默认)或完整 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server NYC Charter, Laws and Rules,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "nyc-charter-laws-rules": { "command": "npx", "args": [ "-y", "@betanyc/nyc-charter-laws-rules" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NYC Charter, Laws and Rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 NYC Charter, Laws and Rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NYC Charter, Laws and Rules,或回答中出现 NYC Charter, Laws and Rules 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NYC_LAWS_INDEX_DIR 从此目录提供索引(结构与 data/index/json/ 相同),而非使用内置索引。 NYC_CLR_FOOTER 可选。每条回复附带的法律免责声明数量:先完整后精简(默认)或完整 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server NYC Charter, Laws and Rules,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "nyc-charter-laws-rules": { "type": "stdio", "command": "npx", "args": [ "-y", "@betanyc/nyc-charter-laws-rules" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NYC Charter, Laws and Rules 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 NYC Charter, Laws and Rules 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NYC Charter, Laws and Rules,或回答中出现 NYC Charter, Laws and Rules 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
NYC_LAWS_INDEX_DIR 从此目录提供索引(结构与 data/index/json/ 相同),而非使用内置索引。 NYC_CLR_FOOTER 可选。每条回复附带的法律免责声明数量:先完整后精简(默认)或完整 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user nyc-charter-laws-rules -- npx -y @betanyc/nyc-charter-laws-rulesClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nyc-charter-laws-rules": {
"command": "npx",
"args": [
"-y",
"@betanyc/nyc-charter-laws-rules"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nyc-charter-laws-rules": {
"command": "npx",
"args": [
"-y",
"@betanyc/nyc-charter-laws-rules"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"nyc-charter-laws-rules": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@betanyc/nyc-charter-laws-rules"
]
}
}
}NYC_LAWS_INDEX_DIR envNYC_CLR_FOOTER env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 BetaNYC 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 @betanyc/nyc-charter-laws-rules@0.5.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/betanyc-nyc-charter-laws-rules)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于今天,最新版本(0.5.0)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 NYC Charter, Laws and Rules | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The single place to access, process, and query New York City's three primary legal documents:
This repo includes:
data/index/json/) for machine usedata/index/markdown/) for human browsing — readable directly on GitHubClone the repo and everything is ready to use. No setup required to browse or query the current index. Run npm run fetch-data && npm run build-index only when you want to refresh from AML.
Vibe coded with Claude by BetaNYC.
[What's changed](WHATS-CHANGED.md): new tools, corrections and other changes a reader would notice, newest first. Daily law text updates are in CHANGELOG.md.
No API key is required. The Charter, Administrative Code, and Rules are served from an offline corpus bundled with the package, so this server works out of the box — no signup, no token, no environment variables to set.
The bundled text is as of the release. An npm install carries the law text from the day that version was published. When the daily refresh picks up new law text, it also publishes a new patch release automatically (see Releases), so the law text in npx -y @betanyc/nyc-charter-laws-rules is normally at most a day behind main's. Code changes ship with the next release. Automatic releases pause while a hand-bumped version is waiting to be published or a release run has failed. get_version reports the dates you are actually serving. To serve main's index directly, see Getting current law text.
Exposes 7 tools over MCP:
| Tool | Description |
|---|---|
search | Keyword search across all three documents (short keyword queries work best) |
get_section | Retrieve a specific section by citation (e.g. § 259, Chapter 11) |
list_titles | List the top-level chapters or titles of a document |
get_title | Retrieve all sections within a chapter or title |
get_version | Return the currency date for each document — so responses can be grounded in exactly how current the law is |
whats_changed | What changed in this server, newest first, from WHATS-CHANGED.md: new tools and corrections |
about_betanyc | Who built this server, where its code is, and where to report a bug in this server or ask for a new feature |
searchKeyword search across the NYC Charter, Administrative Code, and Rules. It is keyword matching, not a question-answering engine, so short keyword queries work best: sidewalk shed rather than "How long can a sidewalk shed stay up?"
"open data" and open data search the same phrase. If any section contains it, those results are returned, relevance-ranked: heading matches rank above citation matches, which rank above body-text matches, and whole-word matches rank above substring matches.how, what, can, a, the, up, about, …) are dropped. The full list is SEARCH_STOPWORDS in src/corpus.ts. Each remaining term matches at the start of a word, with a trailing plural s ignored, so tanks finds "tank" and shed does not find "established". Sections are ranked by how many terms they contain, then by the same heading > citation > body weights.No section contains the exact query; showing sections containing all of: building, owners, required, drinking, water, tanks.No section matched every term; showing sections matching some of: …, or Only 1 section matched every term (listed first); the rest match some of: long, sidewalk, shed, stay.There is no term weighting yet, so a long definitions section that contains every word can outrank the section you want. Ranked full-text search is a separate, later change.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
query | string | yes | — | Search term or phrase |
corpus | string | no | all | charter, admin_code, rules, or all |
limit | number | no | 10 | Max results (max 50) |
search("open data")
search("landlord inspection", corpus="admin_code", limit=20) search("board of health", corpus="rules") search("How long can a sidewalk shed stay up?") # term fallback; first line says so
get_sectionRetrieve a specific section by citation or heading fragment. Input is normalized (with or without §, any case, extra whitespace). If the same citation exists in more than one document (e.g. charter Chapter 3 vs a rules chapter, or a rules section number repeated across titles), a disambiguation list is returned — re-run with the corpus parameter.
| Parameter | Type | Required | Description |
|---|---|---|---|
citation | string | yes | Section citation or heading (e.g. § 259, Section 20-f, 11-602.1, Chapter 11) |
corpus | string | no | charter, admin_code, or rules (default: all three) |
get_section("§ 259")
get_section("11-602.1") get_section("Chapter 11", corpus="charter")
list_titlesList the top-level chapters or titles of a document.
| Parameter | Type | Required | Description |
|---|---|---|---|
corpus | string | yes | charter, admin_code, or rules |
list_titles("charter")
list_titles("rules")
get_titleRetrieve chapter/title records matching an identifier. Matching is whole-token (Chapter 1 does not match Chapter 10). Note: the index is flat — deep hierarchy (every section nested within a title) is not indexed, so this returns matching chapter/title-level records, not full title contents. Title-level indexing is a tracked future feature.
| Parameter | Type | Required | Description |
|---|---|---|---|
corpus | string | yes | charter, admin_code, or rules |
title | string | yes | Chapter or title identifier (e.g. Chapter 11) |
get_title("charter", "Chapter 11")
get_title("admin_code", "Title 6")
get_versionReturn the currency date for each document. Each corpus updates on its own schedule — the Charter and Administrative Code track enacted local laws, while the Rules update independently as agencies adopt new rules.
No parameters required.
get_version()
Example response:
NYC Charter: Current through Local Law 2026/112, enacted June 19, 2026, (854 sections; indexed 2026-06-29T12:33:00.864Z)
Administrative Code: Current through Local Law 2026/112, enacted June 19, 2026, (12587 sections; indexed 2026-06-29T12:33:09.801Z) Rules of NYC: Current through rules effective July 1, 2026. (8671 sections; indexed 2026-07-01T12:43:45.635Z)
whats_changedWhat changed in this server, newest first, from WHATS-CHANGED.md, which ships with the package. Covers new tools, corrections and other changes a reader would notice; daily law text updates are not listed (see CHANGELOG.md). Corrections say what to re-check if you used the old answer. Returns text plus structuredContent matching the tool's outputSchema.
| Parameter | Type | Required | Description |
|---|---|---|---|
since | string | no | YYYY-MM-DD: changes on or after this date |
tag | string | no | Site, Data, MCP or Correction (any case) |
limit | integer | no | 1 to 50, default 10 |
whats_changed()
whats_changed(tag="Correction")
about_betanycWho built the server (BetaNYC, a project of the Fund for the City of New York), its version and repository, where to report a bug in this server or ask for a new feature, and links to BetaNYC. No parameters.
whats_changed and about_betanyc are the two tools BetaNYC is adding to each of its MCP servers. src/betanyc-tools.ts is a copy of the canonical file in BetaNYC's workspace; never edit the copy. Their text ends with the one-line disclaimer (the full one with NYC_CLR_FOOTER=full), and they do not use up the full footer meant for the first law answer.
npm test
npm test builds the TypeScript source first (pretest script), then runs the full suite with node --test. Every test file in the table below runs together. On a laptop the whole run, build included, takes about 4 seconds (measured October 2026).
| File | What it covers |
|---|---|
test/extract-text.test.js | Unit tests for the extractText, normalize, childrenByTag, getAttr, and tagOf helpers in scripts/lib/extract-text.js. Covers inline-LINK document order (issue #3 regression), entity decoding, ALP-marker stripping, enumeration-marker repair, empty/self-closing elements, deep nesting, whitespace-only text nodes, and helper edge cases. |
test/content-leak.test.js | Regression tests for the content-leak fix (PR-A0): undecoded nbsp entities, [ALP S-xxx] editorial markers, and leading-digit run-ons (1Each). Includes scope guards confirming that inline labels with no after them in the source ((6)the) are left untouched. |
test/corpus-invariants.test.js | Invariant assertions over the committed data/index/json/*.json (every section across charter, admin\_code, and rules). Asserts: no run-together text, no subdivision label fused to the next word (a.There, issue #27), no leaked XML tags, no undecoded entities, no double spaces, no leading/trailing whitespace, and structural integrity against versions.json counts. Collects all violations before asserting, with corpus/id/citation/snippet in the failure message. |
test/mcp-tools.test.js | In-process tests for the MCP handler functions (searchCorpus, getSection, listTitles, getTitle, getVersions) imported from dist/corpus.js. Grounded in real index data: verifies § 292 text content (the issue-#3 corrected phrase), negative lookups, version presence, and title listing. |
test/search-fallback.test.js | Plain-language questions (issue #30). Unit tests for stopword and question-word stripping (queryTerms) and surrounding-quote removal (stripSurroundingQuotes). Exact ranks, counts and first-line notices run against a synthetic 8-section index committed at test/fixtures/search-index/, served through NYC_LAWS_INDEX_DIR in a child process: ranking by terms matched, word-start matching (shed is not found in "established"), plural s, the all-terms and widened notices, phrase results unchanged, quoted queries matched as phrases. Against the real index only behavior is checked (fallback used, notice first, terms listed, results non-empty), so a daily refresh cannot turn it red. |
test/index-dir.test.js | The NYC_LAWS_INDEX_DIR override (issue #26), each case in a child process: unset and blank serve the bundled index; a set directory serves its versions and section text; relative paths resolve against the working directory; a directory without versions.json fails at startup naming the variable, with no silent fallback. Also starts the server over stdio and checks that serverInfo.version matches package.json and that get_version reports the override. |
| test/footer-modes.test.js | Disclaimer footer modes (issue #25). NYC_CLR_FOOTER parsing (unset, blan