房脉 PropPulse

房源监测与价格雷达

房脉 PropPulse 是一个聚焦房源监测、价格趋势与降价线索发现的数据平台。 它把公开房源数据、周报快照和手工补样整理成可持续更新的静态 Dashboard，帮助用户更高效地识别买房机会与市场变化。

适用对象

• 买房决策用户
• 房产研究与内容团队
• 顾问 / 中介 / 投资观察者
• 需要长期跟踪小区与价格信号的人

核心能力

• 房源监测：持续跟踪重点小区与目标房源
• 价格趋势：观察均价变化与阶段性信号
• 降价线索：突出识别高优降价样本
• 静态看板：用低成本方式稳定发布可视化结果
• 手工补样：在样本不足时补充可信成交信息

入口

• Repository: https://github.com/sine-io/proppulse
• Site: https://www.sineio.top/proppulse/
• Runbook: docs/RUNBOOK.md

Requirements

• Node.js 22
• npm 10+
• Playwright Chromium for local e2e runs: npx playwright install --with-deps chromium

The GitHub workflows in .github/workflows/collect.yml, .github/workflows/manual-input.yml, and .github/workflows/deploy-pages.yml all use Node 22. Use the same version locally to avoid drift.

Local Commands

Install dependencies for local development:

npm ci

GitHub Actions workflows intentionally use a pnpm-backed install path for runner stability (npm install -g pnpm@9 followed by pnpm install --no-frozen-lockfile). Keep using npm ci locally unless you are specifically reproducing the CI environment.

Run the core checks:

npm run test
npm run typecheck

Collect fresh upstream snapshots:

npm run collect

Build derived data and the static site:

npm run build

Preview the built app locally:

npm run preview -- --host 127.0.0.1 --strictPort

Run the Playwright smoke test against the built app:

npm run build
npm run test:e2e -- tests/e2e/site-smoke.spec.ts

GitHub Pages

GitHub Pages deployment is already defined in .github/workflows/deploy-pages.yml.

To enable it in a repository:

1. Push this repo to GitHub and keep the default branch as main.
2. In GitHub, open Settings -> Pages.
3. Set Source to GitHub Actions.
4. Ensure Actions are enabled for the repository.
5. Push a commit that changes site/**, site/public/data/**, data/config/**, data/series/**, or data/reports/**.

Docs-only commits, including README.md and files under docs/, do not trigger Deploy Pages automatically. If you need to republish after a docs-only change, run Deploy Pages manually with workflow_dispatch in GitHub Actions.

The workflow builds dist/ and deploys it with the official Pages actions.

Issue Forms

The manual sample form lives at .github/ISSUE_TEMPLATE/manual-sample.yml. The ingestion workflow lives at .github/workflows/manual-input.yml.

To configure issue forms:

1. Enable Issues in the repository settings.
2. Keep the form file under .github/ISSUE_TEMPLATE/ with the .yml extension.
3. Update the community and segment dropdown options in manual-sample.yml whenever the monitored config changes.
4. Keep the field markers unchanged unless you also update the validation block in manual-input.yml.

The workflow only accepts issues from OWNER, MEMBER, or COLLABORATOR accounts and rejects bodies that do not match the issue form markers.

Fixture Mode

Fixture mode is for deterministic local verification without upstream network access. npm run collect -- --fixture reads HTML from tests/fixtures instead of live sources.

Safe usage:

tmp_runs_dir="$(mktemp -d)"
npm run collect -- --fixture tests/fixtures --runs-dir "$tmp_runs_dir/runs"

Notes:

• Always pass --runs-dir to a temporary directory when using fixtures. Without it, collect writes to data/runs.
• npm run collect -- --fixture with no path uses tests/fixtures by default.
• Fixture mode is appropriate for tests and dry runs, not for refreshing production data.