erdos-problems 0.2.8 → 0.2.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # erdos-problems
2
2
 
3
+ Maintained by Fractal Research Group (`frg.earth`).
4
+
3
5
  > CLI and workspace for Paul Erdos problems.
4
6
  >
5
7
  > Browse the atlas, scaffold a dossier, and keep public status, local route state, and verification records separate.
@@ -37,6 +39,16 @@ A short example from the first minute:
37
39
  - pack-specific views where this repo already has enough structure to support them
38
40
  - an ORP-based workflow for claims, checkpoints, and run artifacts
39
41
 
42
+ ## Repo, npm, and Upstream
43
+
44
+ - the npm package is the installable CLI plus the bundled atlas snapshot, packaged dossiers, and pack assets
45
+ - the GitHub repo is the central collaboration space for dossiers, pack packets, docs, issues, discussions, and pull requests
46
+ - `.erdos/` is local workspace state created by the CLI; it is not the canonical public collaboration surface
47
+ - `erdos upstream show` tells you whether you are currently using the bundled package snapshot or a workspace-local refreshed snapshot
48
+ - `erdos upstream sync` refreshes a workspace-local snapshot from `teorth/erdosproblems` without mutating the packaged bundle
49
+ - `erdos upstream sync --write-package-snapshot` is the maintainer path for intentionally updating the bundled snapshot in this repo
50
+ - repo-only collaboration files can live in the public repo without shipping in the npm tarball; see the GitHub contribution guide: https://github.com/SproutSeeds/erdos-problems/blob/main/CONTRIBUTING.md
51
+
40
52
  ## Start In 60 Seconds
41
53
 
42
54
  Install:
@@ -45,6 +45,21 @@ The package ships a bundled snapshot of `teorth/erdosproblems` and can refresh a
45
45
  Selected problem families get deeper pack-specific context.
46
46
  The first pack is `sunflower`.
47
47
 
48
+ ## Collaboration model
49
+
50
+ The GitHub repo is the central public collaboration space.
51
+
52
+ - canonical dossiers live under `problems/<id>/`
53
+ - pack-specific packets live under `packs/<family>/`
54
+ - CLI/runtime behavior lives under `src/`
55
+ - local runtime state lives under `.erdos/` and should not be treated as canonical repo truth
56
+
57
+ The npm package is the installable distribution channel, not the only collaboration surface.
58
+
59
+ - the package ships the CLI, bundled upstream snapshot, canonical dossiers, and packaged pack assets
60
+ - the public repo may also contain contribution guides, issue templates, maintainer notes, and other repo-only collaboration files that do not need to ship in the npm tarball
61
+ - workspace-local upstream refreshes should be explicit and inspectable
62
+
48
63
  ## Repository shape
49
64
 
50
65
  ```text
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "erdos-problems",
3
- "version": "0.2.8",
3
+ "version": "0.2.10",
4
4
  "description": "CLI atlas and workspace tools for Paul Erdos problems.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -36,6 +36,7 @@
36
36
  "agents",
37
37
  "sunflower"
38
38
  ],
39
+ "author": "Fractal Research Group <cody@frg.earth>",
39
40
  "dependencies": {
40
41
  "breakthroughs": "^0.1.1",
41
42
  "yaml": "^2.8.3"
@@ -8,7 +8,8 @@ price_checked_local_date: 2026-03-25
8
8
  recommendation: local_scout_first
9
9
  approval_required: false
10
10
  summary: Problem 20 now has a frozen local-scout packet for the uniform k=3 transfer window. The job is to verify a small explicit reduction bundle before any paid compute rung is considered.
11
- source_repo: /Volumes/Code_2TB/code/sunflower-coda/repo
11
+ source_repo:
12
+ name: sunflower-coda
12
13
  public_feature: uniform_k3_frontier
13
14
  rungs:
14
15
  - label: local_scout
@@ -1,4 +1,5 @@
1
1
  import { getProblem } from '../atlas/catalog.js';
2
+ import { getBundledUpstreamDir, getWorkspaceUpstreamDir } from '../runtime/paths.js';
2
3
  import { fetchProblemSiteSnapshot } from '../upstream/site.js';
3
4
  import { buildUpstreamDiff, loadActiveUpstreamSnapshot, syncUpstream, writeDiffArtifacts } from '../upstream/sync.js';
4
5
 
@@ -48,10 +49,18 @@ export async function runUpstreamCommand(args) {
48
49
  return 0;
49
50
  }
50
51
  console.log(`Snapshot kind: ${snapshot.kind}`);
52
+ console.log(`Active source: ${snapshot.kind === 'workspace' ? 'workspace override' : 'bundled package snapshot'}`);
51
53
  console.log(`Upstream repo: ${snapshot.manifest.upstream_repo}`);
52
54
  console.log(`Upstream commit: ${snapshot.manifest.upstream_commit ?? '(unknown)'}`);
53
55
  console.log(`Fetched at: ${snapshot.manifest.fetched_at}`);
54
56
  console.log(`Entries: ${snapshot.manifest.entry_count}`);
57
+ console.log(`Active manifest: ${snapshot.manifestPath}`);
58
+ console.log(`Active index: ${snapshot.indexPath}`);
59
+ console.log(`Active yaml: ${snapshot.yamlPath}`);
60
+ console.log(`Bundled snapshot dir: ${getBundledUpstreamDir()}`);
61
+ console.log(`Workspace snapshot dir: ${getWorkspaceUpstreamDir()}`);
62
+ console.log('Refresh workspace snapshot: erdos upstream sync');
63
+ console.log('Refresh bundled package snapshot (maintainers): erdos upstream sync --write-package-snapshot');
55
64
  return 0;
56
65
  }
57
66