De-fork follow-up: census self-scan exclusion + wire ratchet CI step

Open
#1,016 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
ci-cd, tooling

Research direction

Start with script/upstream/census.ts and the S1 PR (#1013) to understand the existing scan and baseline, then inspect .github/workflows/ci.yml for the deferred ratchet step. Run census.ts --check --ours HEAD, regenerate the 2026-07-18 baseline, and verify the committed HEAD passes with the CI ratchet wired and its ci.yml defork exemption.

Written by the indexing model from the issue text.

Description

Once script/upstream/ is committed (S1, PR #1013), `census.ts --check --ours HEAD` scans its OWN tooling files (analyze.ts, census.ts, bridge-merge.ts, audit-unwrapped.ts, README.md, unclosed-marker-allowlist.jsonc) which legitimately contain `altimate_change start` as code/data — the census parser then throws "unclosed marker" on those string literals.

Fix: census.ts should exclude its own tooling directory (script/upstream/) from the marker scan — scanning the marker-checking tooling for markers is a category error, and those files contain zero real altimate_change blocks (only string-literal false-positives), so excluding them keeps the fork_owned count consistent with the current baseline.

Then: regenerate the 2026-07-18 baseline (should be identical block counts), add the deferred census-ratchet CI step back to .github/workflows/ci.yml (with a defork-exemption for the ci.yml ratchet-step marker), and verify `census.ts --check` passes at the committed HEAD.

Deferred from the S1 PR (#1013) to keep its CI green. The tooling + baselines are correct; only the CI ratchet guardrail wiring waits on this.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.