The snippets, ordered obscure → unmistakable
- Snippet 1(Generic xmalloc)
- Snippet 2(WORD_LIST helpers)
- Snippet 3(Parser fragment)
- Snippet 4(Variable / shell-options)
- Snippet 5(Brace expansion)
- Snippet 6(shell.c version banner)
Why this project gives itself away
The give-away. Snippet 1 is generic. Snippet 2's WORD_LIST / WORD_DESC allocator is Bash's internal word representation — every parameter expansion produces one of these. Snippet 3 names parse_and_execute with setjmp_nosigs/top_level — Bash's longjmp-based error recovery. Snippet 4 lists shopt_vars (extglob, globstar, nullglob) — these are shell options you'd recognise from shopt -s. Snippet 5 is brace expansion ({1..5}) — Bash-specific. Snippet 6 is the bash_copyright / dist_version / patch_level banner from shell.c.
How a Framed puzzle is built
Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.