Skip to content

README: capability-first tagline; badges in a Status section - #496

Merged
swapnilpaliwal-sd merged 1 commit into
mainfrom
readme4
Sep 14, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
mainfrom
readme4

Conversation

@swapnilpaliwal-sd

@swapnilpaliwal-sd swapnilpaliwal-sd commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

The tagline now states the capability (exact call graph through interfaces, inheritance and callbacks; blast radius for people and coding agents) rather than the output format. The badges leave the header for a Status section beside Development, with a note that GitHub cannot render workflow badges for a private repository, which is why the Build (ci.yml, from #418) and Engines (publish-npm.yml, from #478) badges show nothing today; they light up when those PRs merge and the repository is public.

…ges move to a Status section (they cannot render while the repository is private)
@swapnilpaliwal-sd swapnilpaliwal-sd added the documentation Improvements or additions to documentation label Sep 14, 2026
@swapnilpaliwal-sd swapnilpaliwal-sd self-assigned this Sep 14, 2026
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit 0f77c64 into main Sep 14, 2026
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the readme4 branch September 14, 2026 06:56
swapnilpaliwal-sd added a commit that referenced this pull request Sep 14, 2026
…e) (#472)

* javascript: the engine on the reshape layout — graph/javascript, the in-repo parser, a JavaScript bundle adapter and vocabulary, bin/axiom-graph --language javascript

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: callback_registered and event_dispatch edges — a function handed to a call and a handler reached from emit are in the graph; case 09

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* pipeline: the bundle runs from the package root — tsx resolves the @/ alias from the caller's cwd, which failed every solve started outside the repository

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: the torture project with a runtime oracle — self dispatch over constructed subclasses, prototype mixins, rest arrays, literal keys, Reflect.apply, emitter chaining, handler arguments, sort comparators

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: string values, library models (assign-like, inherit-like, Object.create, express handlers), the overwrite flag read the right way round, a CommonJS require binding holds module.exports, library parameters untracked; a real express application scored against execution with node_modules instrumented

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: README — library models, string values, execution oracles

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: the compiler oracle can read installed packages (ORACLE_NODE_MODULES_DEPTH); the scorer identifies staged library methods so client->library edges score like client->client

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript: class field initializers, computed-call and comma-expression callees, numeric/template/computed keys, new-returning-object, property descriptors and the OBJECT_DEFINE_PROPERTY export, promises, generators, JSDoc @this/casts/Map/Set/Promise generics, platform models, export * as ns, the anonymous default class, dotted heritage text, getters as values; ten probe cases join the suite

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* README: Modified front page: quick start first, same numbers (#492)

* README: the front page a reader expects — tagline, quick start first, what you get, how it works, accuracy, layout, development

The substance is unchanged (every measured number is kept); the order and shape follow what
established projects do: what it is in one line, how to run it in three, then depth. Two
open-source project names and two library names are dropped from the public text.

* README: what it does and why coding agents need it, in plain language; the three trust properties; languages with their maturity

* javascript: a superclass named by a parameter — `(Sup) => class extends Sup` takes the class the callers passed; scope_enclosing_method walks the block chain to the owning function

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* README: build and engine-publish status badges instead of a languages badge; language support with logos, parser/engine columns and maturity (#493)

* javascript parser: the four parser-blocked issues — default class targets, dotted superclasses, every re-export's import, destructuring paths (#494)

Fixes #484, #479, #487, #459; the parser half of #483. Parser suite 39/39, corpus 41/41, TypeScript 46/46, Python 21/21, gen_decls --check OK, scrub 0 hits, engine tsc clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* javascript docs: cases 10–19 in the suite README, PD-JS-7..9 (dotted heritage link, missing extends expression, getters), the parser-blocked residue under 'What is not built'

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* README: XML, YAML and Gradle in the language strip, and a configuration-formats table with parser/engine status (#495)

* README: the tagline says what it does, not what format it writes; badges move to a Status section (they cannot render while the repository is private) (#496)

* README: language support reordered (JavaScript, Python, TypeScript, Java, C#); Status section follows Language support

* README: an opening a first-time reader gets in three lines; no em-dashes anywhere (#501)

* javascript: the engine halves of the parser fix (#494) — binding paths walked from a value (pattern variables, pattern-parameter references, a destructured require's dotted importedName), type_super through the linked extends expression, Object.entries as pairs, the default-export recovery joins retired; five known-missing lists emptied

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant